Systems and methods for portals into snapshot data

ABSTRACT

In one embodiment, a user or client device communicates with a distributed file system comprised of one or more physical nodes. The data on each of the physical nodes store metadata about files and directories within the file system. Some of the embodiments permit a user to take a snapshot of data stored on the file system. The snapshot may include a single file, a single directory, a plurality of files within a directory, a plurality of directories, a path on the file system that includes nested files and subdirectories, or more than one path on the file system that each includes nested files and directories. In some embodiments, systems and methods intelligently choose whether to use copy-on-write or point-in-time copy when saving data in a snapshot version of a file whose current version is being overwritten. In some embodiments, systems and methods allow snapshot users to return from a snapshot directory to the immediate parent directory from which the user entered into the snapshot.

CROSS-REFERENCED APPLICATIONS

This application was filed on the same day as the following applications, SYSTEMS AND METHODS FOR ADAPTIVE COPY ON WRITE, application Ser. No. ______ [ISIL.029A], and SYSTEMS AND METHODS FOR READING OBJECTS IN A FILE SYSTEM, application Ser. No. ______ [ISIL.031A], both of which are hereby incorporated by reference in their entirety herein.

LIMITED COPYRIGHT AUTHORIZATION

A portion of the disclosure of this patent document includes material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyrights whatsoever.

FIELD OF THE INVENTION

This invention relates generally to a computer system, and more specifically to taking snapshots of data in a computer system.

BACKGROUND

The amount of data stored on digital computing systems has increased dramatically in recent years. Accordingly, users have become increasingly reliant on the storage devices of these systems to store this data. Typically, the data stored on the storage devices undergo modifications. These modifications may arise from user intervention, periodic system updates or alterations, computer initiated processes, or some other source. Whatever the source of the modifications, it is often useful to preserve and permit access to previous versions of the data such as, for example, files and directories. Some instances of when access to previous versions may be useful include, but are not limited to, inadvertently deleted or overwritten data, providing external access to older versions of data while newer versions are being updated, and determining changes to storage device usage over time.

One response to preserving older versions of files has been to copy the entire contents of the storage device to a backup or second storage device. A digital computing system employing this technique will often encounter numerous problems. One, copying entire data systems is time consuming and delays write requests to data on the storage device. Second, this type of backup is financially expensive because it often requires the purchase of additional storage space. Finally, this option does not permit system flexibility. Backups of portions of the file system can reduce the time and expense encountered with traditional methods.

Moreover, the aforementioned problems are amplified when modern, large-capacity storage devices and distributed storage systems comprising numerous large-capacity storage devices are considered.

Because of the foregoing challenges and limitations, there is a need to provide a more efficient manner in which to provide snapshots of data in a system.

SUMMARY OF THE INVENTION

In general, embodiments of the invention relate to taking snapshots of data in a computer system.

In one embodiment, a method of determining whether to use Copy-On-Write (COW) or Point-In-Time-Copy (PITC) for storing multiple versions of at least a portion of a file is provided. The method may include receiving a request to modify a portion of a file; determining whether to perform a Point-In-Time-Copy operation; if it is determined to perform a Point-In-Time-Copy, performing a Point-In-Time Copy operation on the portion of the file; and if it is determined not to perform a Point-In-Time-Copy, performing a Copy-On-Write operation on the portion of the file.

In another embodiment, a computer-readable medium is provided, having instructions stored thereon for determining, when the instructions are executed, whether to use Copy-On-Write (COW) or Point-In-Time-Copy (PITC) for storing multiple versions of at least a portion of a file. The instructions may include receiving a request to modify a portion of a file; determining whether to perform a Point-In-Time-Copy operation; if it is determined to perform a Point-In-Time-Copy, performing a Point-In-Time Copy operation on the portion of the file; and if it is determined not to perform a Point-In-Time-Copy, performing a Copy-On-Write operation on the portion of the file.

In another embodiment, a storage module is provided, having instructions stored thereon for determining, when the instructions are executed, whether to use Copy-On-Write (COW) or Point-In-Time-Copy (PITC) for storing multiple versions of at least a portion of a file. The storage module may include a computer-readable medium having instructions stored thereon; a processor capable of executing the instructions; and a memory system for storing a copy of at least a portion of a file according to the instructions executed on the processor; wherein the instructions may include: receiving a request to modify a portion of a file; determining whether to perform a Point-In-Time-Copy operation; if it is determined to perform a Point-In-Time-Copy, performing a Point-In-Time Copy operation on the portion of the file; and if it is determined not to perform a Point-In-Time-Copy, performing a Copy-On-Write operation on the portion of the file.

In another embodiment, a method is provided of ascending a file system capable of distinguishing, based on relative depth, between multiple unique paths to the same directory. The method may include receiving a request to ascend from a child directory to an expected parent directory, the expected parent directory being one of multiple possible parent dicrectories; determining the expected parent directory by evaluating, in part, a relative depth value of the child directory; and ascending to the expected parent directory.

In another embodiment, a system is provided of ascending a file system by distinguishing, based on relative depth, between multiple unique paths to the same directory. The system may include a processor; a memory system coupled to the processor, the memory system storing a file system; and a navigation module comprising instructions executable by the processor to operate on the file system, the instructions comprising: receiving a request to ascend from a child directory to an expected parent directory, the expected parent directory being one of multiple possible parent directories; determining the expected parent directory by evaluating, in part, a relative depth value of the child directory; and ascending to the expected parent directory.

For purposes of this summary, certain aspects, advantages, and novel features of the invention are described herein. It is to be understood that not necessarily all such advantages may be achieved in accordance with any particular embodiment of the invention. Thus, for example, those skilled in the art will recognize that the invention may be embodied or carried out in a manner that achieves one advantage or group of advantages as taught herein without necessarily achieving other advantages as may be taught or suggested herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates one embodiment of the connections of physical nodes in one embodiment of a distributed file system.

FIG. 1B illustrates one embodiment of a physical node in a distributed file system.

FIG. 2A illustrates one embodiment of a file system hierarchy indicating one embodiment of snapshots taken on the file system hierarchy.

FIG. 2B (2B-1 and 2B-2) illustrates one embodiment of a file system hierarchy indicating one embodiment of virtual directories used to access snapshot data.

FIG. 3 illustrates one embodiment of elements in an inode data structure.

FIG. 4A illustrates one embodiment of elements of a snapshot tracking file immediately after a snapshot has been created.

FIG. 4B illustrates one embodiment of elements of a snapshot tracking file after modifications have been made to files and/or directories governed by one embodiment of a snapshot.

FIG. 5 illustrates one embodiment of a LIN table and one embodiment of a mini-snapshot.

FIG. 6 illustrates one embodiment of a flowchart of operations for creating a snapshot.

FIG. 7A illustrates one embodiment of a top-level flowchart of operations for modifying a file or a directory.

FIG. 7B illustrates one embodiment of a flowchart of operations for painting files or directories with governing snapshot data.

FIG. 7C illustrates one embodiment of a flowchart of operations for storing snapshot data.

FIG. 7D illustrates one embodiment of a flowchart of operations for modifying a file governed by a snapshot.

FIG. 7E illustrates one embodiment of a flowchart of operations for modifying a directory governed by a snapshot.

FIG. 8 illustrates one embodiment of a flowchart of operations for deleting a snapshot.

FIG. 9 illustrates one embodiment of a flowchart of operations for reading a version of a file.

FIG. 10 illustrates one embodiment of a flowchart of operations for performing a lookup operation on a version of a directory.

FIG. 11 illustrates one embodiment of a flowchart of operations for performing a read directory operation on a version of a directory.

FIG. 12A illustrates one embodiment of a logical model file structure implementation.

FIG. 12B illustrates one embodiment of a physical model file structure implementation.

FIG. 12C illustrates one embodiment of a hybrid model file structure implementation.

FIG. 12D illustrates one embodiment of a log-based model file structure implementation.

FIGS. 13A-D illustrate one embodiment of data structures for one embodiment of creating snapshots of a file, modifying the file, and deleting a snapshot of the file.

FIGS. 14A-D illustrate one embodiment of data structures for one embodiment of creating snapshots of a directory, modifying the directory, and deleting a snapshot of the directory.

FIGS. 15A-B illustrate different embodiments of storing a single file in a distributed manner across a cluster of computer nodes.

FIGS. 17A1-3 illustrate examples of one embodiment of implementing copy-on-write.

FIGS. 17B1-3 illustrate examples of one embodiment of implementing point-in-time-copy.

FIG. 16A illustrates a flowchart of one embodiment of implementing copy-on-write.

FIG. 16B illustrates a flowchart of one embodiment of implementing point-in-time copy.

FIGS. 18A-B illustrate flowcharts of one embodiment of implementing adaptive copy-on-write.

FIGS. 19A-F illustrate various file operations (overwrites and deletions) and the result of implementing one embodiment of adaptive copy-on-write.

FIGS. 20A-E2 illustrate the various file operations illustrated in the embodiment of FIGS. 19A through 19E in more detail.

FIG. 21 illustrates the embodiment of a file system hierarchy illustrated in FIG. 2A, abbreviated to include only the portions of the file system hierarchy that are relevant to a single directory (dir1/).

FIGS. 22A-D illustrate flowcharts of example embodiments of descending and ascending a file system hierarchy with snapshot portals.

FIGS. 23A-23D illustrate example embodiments of returning a snapshot user to the immediate parent of a particular snapshot directory.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Systems, methods, processes, and data structures which represent one embodiment of an example application of the invention will now be described with reference to the drawings. Variations to the systems, methods, processes, and data structures which represent other embodiments will also be described.

For purposes of illustration, some embodiments will be described in the context of a distributed file system. Embodiments of a distributed file system suitable for accommodating embodiments of snapshots disclosed herein are disclosed in U.S. patent application Ser. No. 10/007,003, titled, “SYSTEMS AND METHODS FOR PROVIDING A DISTRIBUTED FILE SYSTEM UTILIZING METADATA TO TRACK INFORMATION ABOUT DATA STORED THROUGHOUT THE SYSTEM,” filed Nov. 9, 2001 which claims priority to Application No. 60/309,803 filed Aug. 3, 2001, U.S. patent application Ser. No. 10/281,467 entitled “SYSTEMS AND METHODS FOR PROVIDING A DISTRIBUTED FILE SYSTEM INCORPORATING A VIRTUAL HOT SPARE,” filed Oct. 25, 2002, and U.S. patent application Ser. No. 10/714,326 entitled “SYSTEMS AND METHODS FOR RESTRIPING FILES IN A DISTRIBUTED FILE SYSTEM,” filed Nov. 14, 2003, which claims priority to Application No. 60/426,464, filed Nov. 14, 2002, all of which are hereby incorporated by reference herein in their entirety.

For purposes of illustration, some embodiments will also be described with reference to updating data structures in a file system using information stored in related data structures of the file system. Embodiments of a file system capable of updating data structures with information stored in related data structures of a file system are disclosed in U.S. patent application Ser. No. 11/255,337, titled, “SYSTEMS AND METHODS FOR ACCESSING AND UPDATING DISTRIBUTED DATA,” and is hereby incorporated by reference in its entirety.

In one embodiment of a distributed file system, metadata structures, also referred to as inodes, are used to monitor and manipulate the files and directories within the system. An inode is a data structure that describes a file or directory and may be stored in a variety of locations including on disk and/or in memory. The inode in-memory may include a copy of the on-disk data plus additional data used by the system, including fields associated with the data structure.

As used herein, a file is a collection of data stored in one unit under a filename. A directory, similar to a file, is a collection of data stored in one unit under a directory name. A directory, however, is a specialized collection of data regarding elements in a file system. In one embodiment, a file system is organized in a tree-like structure. Directories are organized like the branches of trees. Directories may begin with a root directory and/or may include other branching directories. Files resemble the leaves or the fruit of the tree. Files, typically, do not include other elements in the file system, such as files and directories. In other words, files do not typically branch. Although in the illustrated embodiment an inode represents either a file or a directory, in other embodiments, an inode may include metadata for other elements in a distributed file system, in other distributed systems, in other file systems, or other systems.

As used herein, data structures are collections of associated data elements, such as a group or set of variables or parameters. In one embodiment a structure may be implemented as a C-language “struct.” One skilled in the art will appreciate that many suitable data structures may be used.

Some of the figures and descriptions relate to an embodiment of the invention wherein the environment is that of a distributed file system. The present invention is not limited by the type of environment in which the systems, methods, processes and data structures are used. The systems, methods, structures, and processes may be used in other environments, such as, for example, other file systems, other distributed systems, the Internet, the World Wide Web, a private network for a hospital, a broadcast network for a government agency, an internal network of a corporate enterprise, an intranet, a local area network, a wide area network, a wired network, a wireless network, and so forth. It is also recognized that in other embodiments, the systems, methods, structures and processes may be implemented as a single module and/or implemented in conjunction with a variety of other modules and the like.

I. Overview

In one embodiment, a user or client device is connected to a distributed file system comprised of one or more physical nodes (for example, storage devices). The data on each of the physical nodes are arranged according to inodes which store metadata about files and directories within the file system. In particular, each inode points to locations on a physical disk that store the data associated with a file or directory.

Some of the embodiments disclosed herein permit a user to take a snapshot of a data stored on the file system. The snapshot may include a single file, a single directory, a plurality of files within a directory, a plurality of directories, a path on the file system that includes nested files and subdirectories, or more than one path on the file system that each includes nested files and directories.

A path to a file or directory specified to create a snapshot will be referred to herein as “the root of the snapshot.” For example, the command “snap create /ifs/data/dir1” creates a snapshot of directory “dir1” and the files and directories nested within “dir1.” Accordingly, “dir1” is the root of the snapshot. In one embodiment, if the root of the snapshot is a file, then the snapshot is of the file only. Thus, the file is “governed” by the snapshot. If the root of the snapshot is a directory, then the root of the snapshot and all files and directories nested within the root of the snapshot as well as their descendents are governed by the snapshot. Accordingly, in some embodiments, more than one snapshot may govern a particular file or directory.

Additionally, the most current version of data on the file system will be referred to as the “current version,” “HEAD version,” or “active version” whereas, previous versions will be referred to as “snapshot data,” the “snapshot version,” or “past versions.” In one embodiment, if the current version of a file or a directory has been deleted from the system, it is possible for a file or directory to have snapshot versions but not have a current version.

In one embodiment, when a snapshot is created, it is created in constant time. That is, no copying of data is required. Instead, a snapshot is created by creating a snapshot tracking data structure associated with the new snapshot, a mini-snapshot(s) if applicable, and an indication in the governance list field of the metadata structure associated with the root of the snapshot. A snapshot is said to be created in constant time because substantially little time is required to create the snapshot. Accordingly, snapshot creation does not substantially interfere with read requests to files and directories governed by the snapshot. This feature and other features of the embodiments disclosed herein will be described in more detail below.

II. System Architecture

In FIG. 1A, a distributed file system 100 comprises various physical nodes 101, 102, 103, 104, 105 that communicate over a communication medium 106. In one embodiment, the communication medium 106 is the World Wide Web. In other embodiments, as described above, the distributed file system 100 may be comprised of one or more hard-wired connections between the physical nodes or any combination of communication types known to one with ordinary skill in the art.

In the depicted embodiment, the physical nodes are either interfaces 101, 102, such as a personal computer, a mainframe terminal or a client application, or data storage systems 103, 104, 105. It will be appreciated by one with ordinary skill in the art that the distributed file system 100 may comprise one or a plurality of interfaces and one or a plurality of data storage systems. In one embodiment, the interfaces 101, 102 may comprise data storage systems such as, for example, data storage systems 103, 104, and 105.

FIG. 1B illustrates one embodiment of a data storage system 110 of the distributed file system 100. The data storage system 110 comprises several subcomponents which may include, for example, an Input/Output Interface 112 that provides for external communication 116, a snapshot module 113, a processor 115, and a storage device 114. In one embodiment, these subcomponents communicate with one another over a bus 111. In some embodiments, the data storage systems may include only a portion of the depicted subcomponents or only the storage device 114.

In one embodiment, the snapshot module 113 is capable of executing the processes and methods described herein. The word module refers to logic embodied in hardware or firmware, or to a collection of software instructions, possibly having entry and exit points, written in a programming language, such as, for example, C or C++. A software module may be compiled and linked into an executable program, installed in a dynamically linked library, or may be written in an interpreted programming language such as, for example, BASIC, Perl, or Python. It will be appreciated that software modules may be callable from other modules or from themselves, and/or may be invoked in response to detected events or interrupts. Software instructions may be embedded in firmware, such as an EPROM. It will be further appreciated that hardware modules may be comprised of connected logic units, such as gates and flip-flops, and/or may be comprised of programmable units, such as programmable gate arrays or processors. The modules described herein are preferably implemented as software modules, but may be represented in hardware or firmware. Moreover, although in some embodiments a module may be separately compiled, in other embodiments a module may represent a subset of instructions of a separately compiled program, and may not have an interface available to other logical program units.

In one embodiment, the processor 115 receives and processes requests to create snapshots, to delete snapshots, to read snapshot data, to modify data governed by a snapshot, and/or other snapshot related processes. In other embodiments, the processor 115 executes some or all of the processes and/or methods described herein. In yet other embodiments, the processor 115 calls the snapshot module to execute snapshot related processes.

In one embodiment, the storage device 114 stores files and directories of the file system and the inode metadata associated with the files and directories. Examples of the arrangements of files and directories stored on the storage device 114 can be found in FIGS. 2A and 2B. In some embodiments, the storage device may be a physical disk. In other embodiments, the storage device may comprise a plurality of physical disks in communication with one another and/or the bus. In yet other embodiments, the storage device may include a magnetic storage medium, an optical disk, a random access memory, a hard drive, and a partitioned portion of a hard drive.

The data storage system 110 may run on a variety of computer systems such as, for example, a computer, a server, a smart storage unit, and so forth. In one embodiment, the computer may be a general purpose computer using one or more microprocessors, such as, for example, an Intel® Pentium® processor, an Intel® Pentium® II processor, an Intel® Pentium® Pro processor, an Intel® Pentium® IV processor, an Intel® Pentium® D processor, an Intel® Core™ processor, an xx86 processor, an 8051 processor, a MIPS processor, a Power PC processor, a SPARC processor, an Alpha processor, and so forth. The computer may run a variety of operating systems that perform standard operating system functions such as, for example, opening, reading, writing, and closing a file. It is recognized that other operating systems may be used, such as, for example, Microsoft® Windows® 3.X, Microsoft® Windows 98, Microsoft® Windows® 2000, Microsoft® Windows® NT, Microsoft® Windows® CE, Microsoft® Windows® ME, Microsoft® Windows® XP, Palm Pilot OS, Apple® MacOS®, Disk Operating System (DOS), UNIX, IRIX, Solaris, SunOS, FreeBSD, Linux®, or IBM® OS/2® operating systems.

III. User Interface

FIG. 2A illustrates one embodiment of a file system hierarchy indicating one embodiment of snapshots taken on the file system hierarchy. As shown, each of the files and directories within the file system 200 is assigned a unique identifier referred to as a Logical Inode Number (“LIN”). The LIN uniquely refers to the on-disk data structures for the file or directory. For example, the LIN associated with /ifs is 2. Accordingly, this inode will be referred to herein as inode two.

As depicted, the root of the file system 200 is /ifs 201. From here, files and directories branch outward, each with a corresponding inode. In one embodiment, inodes that correspond to directories may have one or more child inodes and possibly even one or more grandchild, great-grandchild inodes, and/or other descendents. In another embodiment, inodes that correspond to files do not have any child inodes. For example, inode four corresponds to the directory /data 203 and has child inodes one hundred, five thousand and nine thousand. The grandchild inodes of inode four include inodes one hundred one, one hundred two, five thousand one and five thousand two; the great-grandchild inodes of inode four include inodes five thousand three and five thousand four. In other embodiments, inodes corresponding to files may have child inodes, grandchild inodes, and so forth.

The dashed lines 221, 222, 223 in FIG. 2A correspond to snapshots of the file system 200. In one embodiment, each of the snapshots has a snapshot identifier (“snapshot ID”). In one embodiment, the snapshot ID provides an indication as to the relative time the snapshot was created. For example, if the snapshot ID of snapshot A is greater than the snapshot ID of snapshot B, it is understood that snapshot A was created after snapshot B. In one embodiment, the snapshot ID is assigned to snapshots based on a monotonically increasing global snapshot counter (“global count”). In other embodiments, the snapshot ID may be randomly assigned or otherwise be unrelated to the relative time the snapshot was created.

In FIG. 2A, snapshot one 221 has snapshot ID 497. The root of snapshot one 221 is data and is represented by the path “/ifs/data/”. Thus, directory data/ 203 is the root of snapshot one 221. Accordingly, data/ 203 and all of the files and directories 204, 205, 206, 207, 208, 209, 210, 211 nested within data/ 203 are governed by snapshot one 221.

Snapshot two 222 has snapshot ID 498. The root of snapshot two 222 is represented by the path “/ifs/data/dir1.” Thus, directory dir1/ 205 is the root of the snapshot two 222. Accordingly, dir1/ 205 and all of the files and directories 207, 208 nested within dir1/ 205 are governed by snapshot two 222. Additionally, because dir1/ 205 is also governed by snapshot one 221, dir1/ 205 and all of the nested files and directories under dir1/ 205 are governed by both snapshot one 221 and snapshot two 222.

Snapshot three 223 has snapshot ID 720. The root of snapshot three 223 is represented by the path “/ifs/data/dir2/dir3/file6”. Thus, file6 212 is the root of snapshot three 223. Because no files or directories are nested within file6 212, file6 212 is the only file or directory governed by snapshot three 223. However, file6 212 is also governed by snapshot one 221 because it is a file nested within data/ 203 which is governed by snapshot one 221.

FIG. 2B illustrates one embodiment of a file system hierarchy indicating one embodiment of virtual directories used to access snapshot data. In the depicted embodiment, snapshot data can be accessed in two ways, (1) through a top-level .snapshot/ directory 263 or (2) through .snapshot/ directories 231, 238, 244, 254 nested within subdirectories of a file system hierarchy.

In the depicted embodiment, current versions of the files and directories within the file system 200 are represented using rectangles (for example, data/ 203). Virtual directories that provide access to snapshot data are represented using double rectangles (for example, .snapshot/ 244). Files and directories associated with snapshot one 221 are represented using ovals (for example, data/ 265); files and directories associated with snapshot two 222 are represented using triangles (for example, data/ 283); and files and directories associated with snapshot three 223 are represented using trapezoids (for example, data/ 284). In one embodiment, the snapshot versions of files and directories on a file system are virtual files and directories.

As shown in FIG. 2B, the top-level .snapshot/ directory 263 is a subdirectory of the root of the file system 201, /ifs. The top-level .snapshot/ directory 263 includes subdirectories for each of the three snapshots: snap1/ 264 for snapshot one 221, snap2/ 274 for snapshot two 222, and snap3/ 278 for snapshot 3 223. Using an operating system-compatible “change directory” command (for example, “cd” for UNIX), a user can access the snapshot data for snapshot one 221 using the path /ifs/.snapshot/snap1 264. Once at this path 264, the file system will appear as the file system at the time snapshot one 221 was created. For example, file6 273 from snapshot one can be accessed using the path /ifs/.snapshot/snap1/data/dir2/dir3/file6 273.

The /ifs/.snapshot/snap2/ subdirectory 274 is similar in many respects to the snap1/ subsidirectory 264. The file system appears as it did at the time of snapshot two 222 was created. However, because snapshot two 222 governs only dir1/ 205 and the files 207, 208 nested within it, the parent directory to dir1/ 275 data/ 283, includes enough information to access the snapshot version of dir1/ 275. As used herein, ancestor directories that are not governed by a snapshot but include children files or directories to navigate to snapshot data are referred to as “mini-snapshots.” For example, though the current version of data/ 203 has as its children file1 204, dir2/ 206, and dir1/ 205, the mini-snapshot of data/ 283 for snapshot two 222 has its only child dir1/ 275.

Mini-snapshots serve as stand-ins for the portions of the directory tree between the file system root 201 and the root of a snapshot. Consequently, snapshot data can be accessed in an intuitive way without being computationally expensive.

For example, the .snapshot/snap3/ directory 278 utilizes three mini-snapshot directories, data/ 284, dir2/ 279, and dir3/ 280 to provide access to the snapshot version of file6 281 governed by snapshot three 223. Accordingly, each of the mini-snapshot directories, do not store information unrelated to accessing file6 281; data/ 284 does not store information related to file1 or dir1/; dir2/ 279 does not store information related to file4; and dir3/ 280 does not store information related to file5.

The embodiment depicted in FIG. 2B also shows how snapshot data can be accessed via .snapshot/ subdirectories nested within the file system hierarchy 230. Each directory that includes (or, in some instances, formerly included) data with a snapshot version also has a .snapshot subdirectory. These .snapshot/ subdirectories 231, 238, 244, 254 are similar to the .snapshot/ subdirectory 263 of /ifs 201 in that they preserve the intuitive feel of the file system 200 when accessing snapshot versions. Accordingly, the .snapshot/ subdirectories 231, 238, 244, 254 also utilize mini-snapshots.

One example of a nested .snapshot/ subdirectory can be found within data/ 203. The .snapshot/ subdirectory 244 includes three subdirectories: snap1/ 282, snap2/ 286, and snap3/ 290. Because data/ 203 is the root of snapshot one 221, the subdirectories and files located within snap1/ 282 appear as the subdirectories and files of data/ 203 at the time that snapshot one 221 was created.

Similarly, dir2/ 206 includes a snapshot/ subdirectory 254 that includes snapshot data related to snapshot one 221, snap1/ 255, and snapshot three 223, snap3/ 260. The data within snap1/ 255 can be accessed as if /ifs/data/dir2/ 206 was accessed at the time that snapshot one 221 was taken. However, the data within snap3/ 260 is limited to only file6 262 because snapshot three 223 only governs file6 262. Accordingly, dir2/ 291 and dir3/ 261 are mini-snapshots that provide access to file6 262.

The snapshot/ subdirectory 238 found within dir3/ 210 also includes data associated with snapshot one 221 and snapshot three 240. Subdirectory snap1/ 239 includes the snapshot versions of file5 241 and file6 242. In contrast, subdirectory snap3/ 240 only includes the snapshot version of file6 243 because file6 212 is the root of snapshot three 223.

Subdirectory dir1/ 205 also includes a .snapshot/ subdirectory 231. Nested within .snapshot/ 231 are subdirectories snap1/ 232 and snap2/ 235. Each of snap1/ 232 and snap2/ 235 include versions of file2 233, 236 and file 3 234, 237 that correspond to the versions of file2 207 and file3 208 at the times that snapshot one 221 and snapshot two 222 were created.

In one embodiment, the .snapshot/ subdirectories 231, 238, 254, 244, 263 are virtual directories that are not explicitly represented on disk. Information necessary to create the snapshot data found in each virtual directory can be found by consulting the inode of the “parent” of the virtual directory and the snapshot tracking data structures associated with each snapshot version of the files and/or directories nested within the parent. The virtual directory can be created by (a) determining which snapshots govern each of the files and directories, and (b) accessing the data associated with each version. In some embodiments, to preserve the intuitive feel of the file system, the subdirectories to the .snapshot/ directories that specify the snapshot version (for example, snap1/ 264, snap2/ 274, and snap3/ 278) are also virtual directories. In other embodiments, the .snapshot/ directories and/or their subdirectory(s) are non-virtual directories that are explicitly represented on disk.

IV. Data Structures

A. Metadata

FIG. 3 illustrates one embodiment of some of the data elements of an inode data structure in a file system. As used herein, the data elements associated with a particular inode data structure are referred to as the metadata for the inode. In one embodiment, each element is a field that stores information about the inode, and the metadata is a collection of the information stored in the fields. As used herein, the metadata associated with a file or directory will be referred to as an inode.

In the depicted embodiment, the fields in the inode metadata structure 300 include, but are not limited to, the mode field 301, the LIN field 302, the last snapshot identifier field (“last snapshot ID”) 303, and the governance list field 304. In other embodiments, the metadata structure 300 may include fewer or more fields, such as a reverse lookup hint field, a name field, and/or a field indicating the amount of data referenced by the inode. In addition, the metadata structure may be stored using a different type of data structure.

The mode field 301, indicates, for example, whether the inode corresponds to a file or a directory.

As stated previously, the LIN 302 is a unique identifier in the file system for the inode.

The governance list field 304 includes all of the snapshot IDs that govern the particular inode. In other words, if the inode corresponds to a version(s) of a file or directory, the snapshot ID associated with the version(s) appears in the governance list of the inode. For example, when a snapshot of a file or a directory is created, but before any modifications to the file or directory have been made, the governance list of the current version will include the snapshot ID of the newly created snapshot. However, when that file or directory is modified, the inode associated with the snapshot version will have the snapshot ID in the governance list and the current version will store an empty set in its governance list. Accordingly, a current version of a file without any snapshot versions will also store an empty set in its governance list. The governance list may be implemented using a variety of data structures known to one with ordinary skill in the art such as a linked list or an array.

The last snapshot ID field 303 includes information about the corresponding file or directory that was modified. After modification, the version of the modified file or directory is updated or “painted” with the global count (that is, the snapshot ID at the time the modification is made). In one embodiment, updating the inode with the global count serves to indicate the last time the governance list of the inode was modified.

In one embodiment, the metadata is implemented using an array. In another embodiment, the metadata is implemented using a linked list. A person with ordinary skill in the art will recognize that the metadata can be implemented using a variety of data structures.

B. Snapshot Tracking File

In one embodiment, a snapshot tracking data structure (or, “snapshot tracking file”) is created each time a snapshot is created. Accordingly, a snapshot tracking file is associated with each snapshot. The snapshot tracking file provides information regarding each file or directory governed by a snapshot that was modified or deleted after the snapshot was taken.

In one embodiment, the snapshot tracking file can be used to determine which files and directories of a particular version are examined when deleting a snapshot. In another embodiment, the snapshot tracking file can be used to track information about a particular snapshot. This information may include, but is not limited to, disk usage.

FIG. 4A illustrates one embodiment of elements of a snapshot tracking file 310 immediately after a snapshot has been created. The snapshot tracking file 310 can include several fields such as, for example, a snapshot tracking file LIN field (not shown), a snapshot ID field 311, and LIN fields(s) 312, 313, 314, 315, 316, 317. In other embodiments, the snapshot tracking file 310 may include fewer or more fields than those depicted in FIG. 4A.

In one embodiment, the snapshot tracking file LIN field is a unique identifier associated with the snapshot tracking file 310, and is similar in purpose to the LIN associated with a file or a directory.

In one embodiment, the snapshot ID field 311 is the genesis snapshot ID of the snapshot that the snapshot tracking file 310 corresponds to. In one embodiment, the genesis snapshot ID is equal to the global count at the moment the corresponding snapshot was created. In another embodiment, the snapshot ID field 311 is equal to the time or a representation of the time that the snapshot was created. In yet another embodiment, the snapshot ID field 311 is some other identifier that indicates a correspondence with a related snapshot.

In one embodiment, the LIN field(s) 312, 313, 314, 315, 316, 317 stores the LINs associated with files or directories that have been modified or deleted from the file system after the corresponding snapshot was created. In another embodiment, the LIN field(s) stores the LINs of files or directories that have been read after the snapshot was created. In yet another embodiment, the LIN field(s) stores the LINs of files and directories accessed before a subsequent snapshot is created. While FIG. 4A illustrates a set of six LIN fields, it is recognized that a wide number of LIN fields may be included and/or a variable number of LIN fields may be used, depending on the number of modified LINs.

FIG. 4B illustrates one embodiment of elements of a snapshot tracking data structure 310 after modifications have been made to files and/or directories encompassed by one embodiment of a snapshot. As explained below, with reference to FIGS. 13A-D, the LINs of files and directories modified after snapshot one 221 was taken are added to the snapshot tracking file associated with snapshot ID 497. For example, file4 209 with LIN 5001, file5 211 with LIN 5003, and file6 212 with LIN 5004 were either modified or deleted after snapshot one 211 was taken.

In one embodiment, the snapshot tracking file 310 is a fixed-length array that stores empty sets for LIN fields 312, 313, 314, 315, 316, 317 that have not yet been populated. In other embodiments, the snapshot tracking file 310 is a linked list that adds entries each time a file or directory is modified or deleted. A person with ordinary skill in the art will recognize that a snapshot tracking file can be implemented using a variety of suitable data structures.

C. LIN Table

FIG. 5 illustrates one embodiment of a LIN table 430 and one embodiment of a mini-snapshot 440. In one embodiment, the LIN table stores the LIN/snapshot ID pairs of all of the files and directories in the system. Accordingly, each LIN/snapshot ID pair references the corresponding inode version of a file or directory using, for example, a pointer.

In one embodiment, the LIN table 430 comprises a plurality of rows 431, 432, 433. Each row stores data for a particular version of a file or a directory. Each row 431, 432, 433 is comprised of several fields 467, 468, 469, 470 which may include, but are not limited to, a LIN field 467, a snapshot ID field 468, a mini-snapshot flag 469, and a reference (or, pointer) field 470. In another embodiment, the LIN field 467 and the snapshot ID field 468 comprise a single field. For example, the LIN/snapshot ID pair may be represented using a sixteen byte binary value, with the LIN occupying the most significant bits of the sixteen byte value and the snapshot ID occupying the least significant bits. In another embodiment, the LIN table 430 may include fewer or more fields, such as, for example, the mode, the governance list, the creation date, and so forth.

The LIN field 467 includes the LIN of the inode version that a particular row 431, 432, 433 in the LIN table 430 references.

The snapshot ID field 468 includes the genesis snapshot ID of the inode version that a particular row 431, 432, 433 in the LIN table 430 references.

In one embodiment, the mini-snapshot flag field 469 indicates whether a directory is a mini-snapshot rather than a version of a directory in the file system. In some embodiments, a mini-snapshot is indicated when the flag is set. In other embodiments, a mini-snapshot is indicated when the flag has been cleared.

In one embodiment, the reference field 470 includes a pointer to the inode that corresponds to a LIN/snapshot ID pair represented in the LIN table. For example, row 431 includes the LIN/snapshot ID pair (4, 701) which points to inode 450. Accordingly, inode four hundred fifty includes in its metadata the same LIN 452. Also, inode four hundred fifty includes a governance list 453 that provides a representation of the snapshots that govern this version of inode four hundred fifty. In one embodiment, the governance list 453 does not store the same value(s) as the genesis snapshot ID 468 stored in the LIN table 430.

In some embodiments, the LIN table 430 references inodes 440, 450, 460 that further reference metatrees 443, 454, 467. Metatrees are data structures specific to a version of a file or directory. In one embodiment, metatrees 443, 454, 467 associated with a directory inode store references to the children of the inode. For example, the metatree 467 for inode four stores references to children with LIN one hundred 464, LIN five thousand 465, and LIN nine thousand 466. Thus, the current version of inode four has three children. Metatree 443 has only one entry because it is a mini-snapshot for a file or directory nested within inode one hundred. Therefore, though the current version 460 and a previous version 450 indicate that inode four has three children, the inode 440 associated with the mini-snapshot only references the child 443 necessary to access data governed by snapshot 736.

Row 432 in the LIN table 430 has the mini-flag set in the mini-snapshot flag field 469. In the depicted embodiment, when the flag is set, the row in the LIN table 430 references a mini-snapshot. Accordingly, row 432 references inode 440 which is a mini-snapshot associated with snapshot ID 736. In one embodiment, the metadata for an inode associated with a mini-snapshot does not include a governance list. In this embodiment, a governance list is not needed because no data stored in the data blocks of the inode can be altered because subsequent “versions” of mini-snapshots cannot exist. That is, mini-snapshots are only used to facilitate downward navigation to snapshot data.

Row 433 in the LIN table 430 references inode 460. In one embodiment, the snapshot ID associated with row 433 is “MAX_INT.” MAX_INT represents a binary value wherein all of the bits are set (for example, all bits are set to “1”). In one embodiment, the value MAX_INT is used to represent the current version of a file or directory. For example, whenever the user wishes to modify a file or directory with snapshot ID MAX_INT, the user knows that the current version of the file is being modified. In another embodiment, the current version can be assigned a snapshot ID wherein all bits are cleared (for example, all bits are set to “0”). In a further embodiment, the current version can be assigned a snapshot ID with an empty set or some other representation that identifies the current version.

In one embodiment, each row 431, 432, 433 is implemented using a fixed length array. In another embodiment, each row 431, 432, 433 is implemented using a linked list. In yet another embodiment, the rows are associated with one another using an array or a linked list. A person with ordinary skill in the art will recognize that the LIN table can be implemented using a variety of different data structures.

V. Snapshot Creation

FIG. 6 illustrates one embodiment of a flowchart of operations 400 for creating a snapshot. In the depicted embodiment, the process 400 executes when a snapshot is created. The process 400 begins 401 by getting the path of the root of the snapshot to be created 402. In one embodiment, the root of the snapshot is the top-most level in the file system hierarchy governed by the snapshot. Accordingly, the snapshot governs the root of the snapshot and the descendents of the root of the snapshot. In one embodiment, the root of the snapshot is either a file or directory. In other embodiments, the root of the snapshot is only a file or only a directory.

Next, a snapshot tracking file 310 is created 403 with fields including, for example, the snapshot ID field 311 and the LIN field(s) 312, 313, 314, 315, 316, 317 empty. Then, the global count is accessed and added to the snapshot ID field 311 of the snapshot tracking file 310.

After the snapshot tracking file has been created 403 and the global count added 404, decision block 405 determines whether the root of the snapshot is also the root of the file system. If it is the root of the file system, the operations in blocks 406, 407, and 408 can be skipped. However, if it is not the root of the file system, a for loop for all ancestors of the root of the snapshot to the root of the file system 406 is initiated.

For all of these ancestors, a mini-snapshot is created 407. In one embodiment, creating a mini-snapshot includes two steps. First, an inode is created. The inode comprises at least a mode field and a LIN field. In one embodiment, the mode field indicates that the inode is associated with a directory because, in the exemplary embodiment, files cannot have children. In other embodiments, where either files or directories may have children, the mode field indicates either a file or a directory. The LIN field indicates the LIN of the corresponding ancestor of the root of the snapshot. Second, a reference is created that points to a child of the ancestor in the path to the root of the snapshot. In some embodiments, a mini-snapshot is a virtual data structure that is created when a snapshot version with mini-snapshots is accessed.

In one embodiment, after the mini-snapshots for all ancestors up until, but not including, the root have been created 407, the for loop ends 408. In another embodiment, the for loop ends 408 when mini-snapshots have been created 407 for all ancestors including the root directory. After the for loop ends 408, the genesis snapshot ID is added to the governance list of the inode associated with the current version of the root of the snapshot 409.

In another embodiment, multiple paths to multiple roots of a snapshot are accepted. It is recognized that a person with ordinary skill in the art would be capable of modifying process 400 to accommodate a snapshot that has multiple roots.

While FIG. 6 illustrates one embodiment of a create snapshot operation, it is recognized that other embodiments may be used. For example, the inputs and outputs may be passed as values, references, and/or stores in an accessible memory location.

VI. Copy On Write

FIG. 7A illustrates one embodiment of a top-level flowchart of operations 600 for modifying a file or a directory. Because the operations needed for modifying a file or a directory, in some instances, involve copying data only in response to a write request, some of the operations discussed herein will be referred to as a “copy on write” (“COW”). Moreover, in the depicted embodiment, the top-level flowchart of operations calls various processes 602, 604, 605, 607 in order to complete the operation. In other embodiments, some or all of these processes may comprise a single process. In yet other embodiments, process 600 may be embodied as a single process.

The process 600 of modifying a file or directory begins 601 by executing the painting operation 602 depicted in FIG. 7B. After the painting process 602 terminates 636, decision block 603 determines whether the file or directory that will be modified is governed by a snapshot. The painting process 602, in part, can determine whether the file or directory is governed by a snapshot. If the file or directory is governed by a snapshot, then the create snapshot version of file or directory process 604 is executed. However, if the file or directory is not governed by a snapshot, the create version of file or directory process 604 is skipped.

Next, decision block 606 determines whether a file or a directory is being modified. If a file is being modified, the file COW process 605 is executed. However, if a directory is being modified, the directory COW process 607 is executed. Then, after either the file COW process 605 or the directory COW process 607 finishes executing, the operation ends 608.

While FIG. 7A illustrates one embodiment of a create snapshot operation, it is recognized that other embodiments may be used. For example, the inputs and outputs may be passed as values, references, and/or stores in an accessible memory location.

A. Painting

FIG. 7B illustrates one embodiment of a flowchart of operations 602 for painting files or directories with governing snapshot data. In one embodiment, painting is used because the governance list of a file or directory is not updated each time a snapshot that governs the file or directory is created. For example, if in FIG. 2A, when snapshot one 221 was created, only the governance list of data/ 203 is “painted” with the snapshot ID of snapshot one 221 because it is the root of the snapshot. Faster snapshot creation is facilitated by only painting the root of the snapshot. However, before modifying a file or directory within data/ 203, the process traverses up the tree to data/ 203 to discover whether the file or directory is governed by snapshot one 221. In other embodiments, files and directories governed by a snapshot are painted when the snapshot is created. In these embodiments, painting a file or directory before modifying with a list of governing snapshots is unnecessary.

In one embodiment, the painting process 602 begins 620 at decision block 621 by asking whether the last snapshot ID stored in the file or directory to be modified (or “target file/dir”), is less than the global count. As discussed previously, the global count can be used to indicate the relative time when a snapshot was created or when the governance list of a particular inode was updated. Thus, in the depicted embodiment, the global count is a value that is greater than or equal to any snapshot ID stored in the system. If the last snapshot ID is not less than the global count, then we know that the snapshot ID is equal to the global count and the governance list of the inode is, therefore, up to date. Then, the process ends 636.

However, if the last snapshot ID is less than the global count 621, two variables are initialized 622: EXAMINED MINIMUM=last snapshot ID+1; and EXAMINED DIRECTORY=parent inode of the target file/dir. Next, a while loop initiates 623 and executes the operations nested within it while EXAMINED MINIMUM is less than or equal to the global snapshot count. Therefore, even if the snapshot ID was one less than the global count, the operations in the while loop will execute at least once because EXAMINED MINIMUM must be greater than the global snapshot count to terminate the while loop 623.

Next, a for loop 624 considers each inode version of the EXAMINED DIRECTORY. Within for loop 624, is nested for loop 625 which considers snapshot ID in the governance list of the considered inode version.

Thus, for each snapshot ID of a particular inode version, decision block 626 asks whether the snapshot ID is greater than or equal to EXAMINED MINIMUM. If it is not, the next snapshot ID is considered 628. In other words, if the snapshot ID is not greater than or equal to EXAMINED MINIMUM, the governance list of the target file/dir was updated after the particular snapshot was taken. Thus, the snapshot ID is ignored because it would already be included in the governance list of the target file/dir.

However, if the snapshot ID is greater than or equal to EXAMINED MINIMUM 626, the snapshot ID is added to the governance list of the target file/dir 627. In other words, the snapshot associated with the particular snapshot ID is more recent than the last time the target file/dir was painted 626. Thus, the governance list of the target file/dir is updated 627.

Next, after each snapshot ID in a particular version has been considered, the for loop ends 628 and the next version of EXAMINED DIRECTORY, as dictated by for loop 624, is considered. Then, after all of the snapshot IDs of all of the inode versions of EXAMINED DIRECTORY have been considered, for loop 624 ends 629.

Decision block 630 then determines whether EXAMINED DIRECTORY is the root of the file system. If it is the root of the file system, the while loop 623 breaks 631. After breaking 631, the last snapshot ID field of the target file/dir is updated with the global snapshot count 635 to indicate when it was last painted. Then, the painting process 602 ends.

However, if EXAMINED DIRECTORY is not the root of the file system 630, EXAMINED MINIMUM is assigned a value equal to the greater of EXAMINED MINIMUM and last snapshot ID of EXAMINED DIRECTORY+1 632. In other words, block 632 determines whether the EXAMINED DIRECTORY or the child of the EXAMINED DIRECTORY (which was previously considered by for loops 624 and 624) was last painted. Then, if EXAMINED DIRECTORY is not out of date, as determined by the global snapshot count and the condition presented in the while loop 623, EXAMINED DIRECTORY is updated to be the parent of the previous EXAMINED DIRECTORY (given these conditions, a trivial operation) 633, and the while loop 623 ends 634 because EXAMINED MINIMUM is equal to the global count. Then, the last snapshot ID field of the target file/dir is updated with the global count to indicate when it was last painted 635, and the process ends 636.

Alternatively, if EXAMINED MINIMUM is still less than or equal the global snapshot count, the operation of reassigning EXAMINED DIRECTORY to the parent of the previous EXAMINED DIRECTORY 634 is meaningful because the snapshot IDs of all inode versions of the new EXAMINED DIRECTORY are considered in order to update the governance list of the target file/dir 627. The while loop persists until one of two conditions occur: the EXAMINED DIRECTORY is the root of the file system 631 or the EXAMINED DIRECTORY is one that is not out of date 634. When either of these conditions occur, as explained above, the last snapshot ID of the target/file directory is updated 635 and the process ends 636.

While FIG. 7B illustrates one embodiment of a painting operation, it is recognized that other embodiments may be used. For example, the process may also paint ancestors of the target file/dir or may use other looping instructions. Alternatively, the inputs and outputs may be passed as values, references, and/or stores in an accessible memory location.

B. Creating A Snapshot Version

FIG. 7C illustrates one embodiment of a flowchart of operations 604 for creating a snapshot version. In one embodiment, process 604 creates an inode associated with the snapshot version of a file or directory. Thus, by copying the inode of the target file/dir, creates metadata associated with a snapshot version of the file.

In one embodiment, the creating a snapshot version process 604 begins 610 by adding the LIN of the target file/dir to the snapshot tracking file associated with the governing snapshot 611. As stated previously, a list of all modified files or directories governed by a snapshot can be used when deleting the snapshot or performing other functions. Next, the inode of the target file/dir is copied 612. The copy is then added to the LIN table 612. The LIN table stores the LIN of the target file/dir and the highest snapshot ID in the governance list of the file to be modified. Then, the create snapshot version process 604 ends.

While FIG. 7C illustrates one embodiment of a creating a snapshot version operation, it is recognized that other embodiments may be used. For example, the inputs and outputs may be passed as values, references, and/or stores in an accessible memory location.

C. File: Copy On Write

FIG. 7D illustrates one embodiment of a flowchart of operations 605 for COWing data associated with a modified file. The file COW process 605 copies data from the version of the target file to a previous version of the file before permitting modification of the current version. Thus, the snapshot version preserves the previous version of the file. In the depicted embodiment, the process 605 performs a COW based on units consisting of data blocks. Only the data blocks of the file are written back to the snapshot version. The data blocks can vary in size and can be, for example, 1 bit, 8 bytes, 1 megabyte, 100 megabytes, or 1 gigabyte. In other embodiments, the entire file is copied to a snapshot version before the current version is modified.

In the depicted embodiment, the process 604 begins 640 in decision block 641 which determines whether there is a previous version of the target file. If there is not a previous version of the target file, the version of the target file can be modified 646 without performing a COW. A COW is unnecessary when a version of the target file does not have a previous version because that version does not need to be preserved. After the version of the target file has been modified 646, the process ends 647.

However, if there is a previous version of the target file, decision block 642 asks whether there is a ditto record or indicator for the block address location(s) (“BADDR”) to be modified in the previous version. As used herein, BADDRs are used to refer to the physical address of a data block on disk. In the illustrated embodiments, files are comprised of inodes which store the metadata. The inode references a plurality of BADDR locations stored in a metatree. The BADDR locations can either point to a data block located on a physical disk or reference the next version of the target file (referred to herein as a “ditto record”). If a BADDR location is accessed and it includes an address, then it will use the address to locate data on the physical disk. However, if the BADDR location includes a ditto record, the process will look to that BADDR location in the metatree of the next most recent version. If a ditto record is located in that BADDR location, the process will look to the BADDR location in the metatree of the same BADDR location in the metatree of the next most recent version. This process continues until a BADDR location is reached that includes an address. Then, the data is retrieved from the physical disk or the cache.

In one embodiment the metatree is comprised of an array. In other embodiments, the metatree is comprised of a linked list. In yet other embodiments, the metatree is comprised of a hybrid of a linked list and a plurality of arrays. A person with ordinary skill in the art will recognize that other data structures are considered suitable for storing information related to file data.

In decision block 642, if a ditto record is not found at a BADDR location(s), an address has been found. Thus, the data has already been COWed to the BADDR location(s). In other words, the corresponding BADDR location(s) has been modified at least once the snapshot was created. Therefore, the BADDR location(s) can be modified in the current version 646 directly and the process ends 647.

However, if a ditto record exists at the BADDR location(s), the ditto record is removed 644. Then, data from the BADDR location(s) of the target file is copied to the BADDR location(s) of the previous version 645. Next, the BADDR location(s) of the target file are modified 646 and the process ends 647.

While FIG. 7D illustrates one embodiment of a file COW operation 605, it is recognized that other embodiments may be used. For example, the inputs and outputs may be passed as values, references, and/or stores in an accessible memory location. Additionally, other embodiments may represent and store data common to more than one version using different data structures such as, for example, using a physical model, a hybrid model or a log-based model.

D. Directory: Copy on Write

FIG. 7E illustrates one embodiment of a flowchart of operations 607 for COWing data associated with a modified directory. The directory COW process 607 copies references to old versions of files and directories before permitting modification. In the depicted embodiment, an inode associated with a directory references a metatree that stores information about the child inodes located within the directory. In some embodiments, information about child inodes includes, but is not limited to, the name associated with the child inode, the LIN of the child inode, and the genesis snapshot ID associated with a particular version of the child inode. In other embodiments, less or more information may be stored in the metatree such as, for example, the size of the file or directory associated with the child inode.

In the depicted embodiment, process 607 begins 650 in decision block 651 by determining whether the entry is being added to a target directory or whether an entry within the target directory is being modified or removed. In one embodiment, if an entry is being added to the current version, it is unnecessary to COW the new entry because previous versions of the target directory do not include the new entry. Consequently, the entry can be added to the metatree associated with the target directory 652. Then, the genesis snapshot ID of the entry in the metatree of the target directory is set to the global snapshot count 657 and the process ends 658.

If, however, an entry in the target directory is being modified or removed, decision block 654 asks whether the genesis snapshot ID of the entry is more recent than the most recent snapshot ID in the governance list of the target directory. If the snapshot ID of the entry is more recent than the most recent governing snapshot, the entry is not governed by a snapshot. Therefore, the entry can be removed or modified 655 without COWing the entry to a previous version of the target directory.

However, if the snapshot ID of the entry is not as recent as the latest governing snapshot, the entry is copied to the next-most previous version of the target directory 655 before the target directory can be removed or modified 656. In some embodiments, the entry is copied to the same location in the metatree of the previous version.

After the target directory has been modified, the genesis snapshot ID of the entry is set to the global count 657, and the process ends 658.

While FIG. 7E illustrates one embodiment of a directory COW operation 607, it is recognized that other embodiments may be used. For example, an entry may be added, removed or modified in any version of the directory. Additionally, the inputs and outputs may be passed as values, references, and/or stores in an accessible memory location.

VII. Snapshot Deletion

FIG. 8 illustrates one embodiment of a flowchart of operations 480 for deleting a snapshot. Snapshot deletion is a useful tool for freeing physical disk resources. For example, suppose a portion of a file system is used to develop an upcoming software release. Also suppose that snapshots are taken of that portion on a daily basis in order to preserve changes to files during the development process. When the software is released, there may no longer be a need to access previous versions of the software. Therefore, a system administrator can utilize the delete snapshot operation of FIG. 7 in order to free disk space occupied by previous versions. In one embodiment, snapshots older than a specified time may be deleted. In another embodiment, snapshots that fall between a specified time range may be deleted. In the depicted embodiment, a single snapshot is deleted.

The delete snapshot process 480 begins 481 by accepting a delete snapshot request 482 from a user, client application, application, or other source. Next, a for loop 483 considers all files and/or directories in the snapshot tracking file. As previously discussed, in one embodiment, the snapshot tracking file comprises a list of all files and directories that were modified or deleted after the snapshot was created.

For each considered file, decision block 484 asks whether a previous snapshot governs the snapshot to be deleted. If there is not a previous governing snapshot, the snapshot version of the considered file or directory can be deleted 491. In one embodiment, the version of the file or directory is deleted without any copy operations because previous versions do not store data referenced by future versions.

Next, the inode associated with the snapshot of the considered file or directory is deleted 492. Then the LIN/snapshot ID pair for the considered version of the file or directory is deleted from the LIN table 493. Then, for loop 483 considers the next file or directory in the snapshot tracking file.

However, in decision block 484, if there is a previous snapshot, decision block 485 asks whether a file or directory is being considered by the for loop 483. If a file is being considered, data is copied to BADDR locations in a previous version of the file if the particular BADDR location includes a ditto entry referencing the deleted snapshot.

If, however, decision block 484 considers a directory, for loop 487 considers each file or directory referenced by the directory considered by for loop 483. For each referenced file or directory, process considers whether the snapshot ID of the referenced file or directory is less than or equal to the highest snapshot ID in the governance list of the previous snapshot 488. If it is, the reference to the file or directory is copied to the previous version. This comparison of snapshot IDs determines whether the referenced file or directory was created after the next-most previous snapshot was created. Thus, if the referenced file or directory was created after the previous snapshot, then COWing the referenced file or directory is unnecessary because the referenced file or directory did not exist at the time the previous snapshot was created. After all of the referenced files or directories have been considered, the for loop 487 ends 489.

After the file or directory in the snapshot tracking file has been COWed 486, 488, operations 492 and 493 execute. Then, after all of the files and directories in the snapshot tracking file have been considered, the for loop 483 ends 490. Next, the snapshot tracking file associated with the snapshot is deleted 494, and the delete snapshot process 480 ends 495.

While FIG. 8 illustrates one embodiment of a delete snapshot operation 480, it is recognized that other embodiments may be used. For example, the inputs and outputs may be passed as values, references, and/or stores in an accessible memory location.

VIII. Read File

FIG. 9 illustrates one embodiment of a flowchart of operations 700 for reading a version of a file governed by a snapshot. In the depicted embodiment, the metatree is the current version of a file includes addresses in all of its BADDR locations. That is, no ditto records are found in the current version. Thus, the current version can be read directly by accessing the metatree and referencing the indicated locations on the physical disk. However, when accessing a snapshot version of a file, some BADDR locations may include a ditto record. For these BADDR locations, subsequent versions of the file need to be accessed until a location is reached that includes an address (“a real BADDR record”).

In one embodiment, the read file process 700 begins 701 by receiving the LIN of the file version to be read 702 and the snapshot ID of the file version 703. In another embodiment, the path to the file version is received. In one embodiment, the snapshot ID of the file version 703 is stored in an in-memory cache structure. In embodiments that utilize the user interface described with respect to FIG. 28, the path includes a .snapshot/ subdirectory if a snapshot version is sought.

Next, the process gets the inode that corresponds to the received LIN/snapshot ID pair. This step can be performed using lookup techniques known to those with ordinary skill in the art.

After the inode has been retrieved, a for loop 705 considers each BADDR location in the portion of the metatree being read. Then, for each BADDR location, decision block 706 asks whether there is a real BADDR record exists. If a real BADDR record exists, the process looks up the BADDR on the physical disk 708 and retrieves data. However, if a real BADDR record does not exist, the process reads the next inode version 707. Again, the process will determine if a real BADDR record exists in the next version 706. The process will continue looking to subsequent versions 707 until it finds a real BADDR record in the considered BADDR location. When a real BADDR record is found, the process looks up the BADDR on the physical disk 708 and retrieves the data.

After all of the BADDR locations in the portion of the metatree being read have been considered, the for loop ends 709 and the read file process ends 710.

While FIG. 9 illustrates one embodiment of a read file operation 700, it is recognized that other embodiments may be used. For example, the inputs and outputs may be passed as values, references, and/or stores in an accessible memory location.

IX. Directory Lookup

FIG. 10 illustrates one embodiment of a flowchart of operations for performing a lookup operation 800 on a version of a directory governed by a snapshot. This process permits a user or client application to determine whether a target file or directory is located in a particular snapshot version of a directory. For example, if the user or client application wants to access the version of a target file at the time a particular snapshot was created, process 800 determines whether the target file existed at the time of the snapshot. If the target file did exist for that snapshot, the process returns the location of the file. However, if the target file did not exist for that snapshot, the process returns an indication that the target file could not be found.

In one embodiment, the directory lookup process 800 begins 801 by receiving a target file or directory. The target file or directory is the version of a file or directory a user or client application wishes to access from a particular snapshot. Next, the process receives the LIN/snapshot ID of the particular snapshot 803, the “relevant snapshot,” of a parent directory, the “relevant directory,” that may or may not include the target file or directory.

Then, a for loop 804 considers all snapshots of the relevant directory that have a snapshot ID greater than or equal to the snapshot ID of the relevant snapshot. In one embodiment, the range of snapshots are considered from oldest to newest. Considering the snapshots in this way can speed up the lookup operation for target files or directories that have been modified frequently. That is, if the target file or directory has been modified frequently, the COWed version of the target file or directory is more likely to appear as an entry in an older version of the relevant directory rather than a newer version of the relevant directory. In other embodiments, the for loop 804 considers the range of snapshots from newest to oldest. Considering snapshots in this order is more efficient for target files directories that are rarely, if ever, modified because they are more likely to appear in a newer version of the relevant directory.

For the snapshot being considered, the process performs a lookup in the metatree of the relevant directory for the target file or directory. In other embodiments, the lookup may be performed in another data structure that stores entries corresponding to the children of the relevant directory.

Next, decision block 806 asks whether an entry matching the target file or directory is found in the metatree of the considered version of the relevant directory. If it is not, the next snapshot is considered 804 and the lookup is repeated 805. However, if a matching entry is found in the considered version, decision block 807 asks whether the genesis snapshot ID of the matching entry is less than the snapshot ID of the relevant version. If the genesis snapshot ID of the entry is less than the snapshot ID of the relevant version 807, the for loop breaks 809 and the location or path of the appropriate version of the target file or directory is returned 811. Then, the process 800 ends 810.

However, if the genesis snapshot ID of the matching entry is not less than the snapshot ID of the relevant version 807, the matching entry was a version created after the relevant snapshot and was, therefore, not an entry in the relevant version of the relevant directory. The process then considers the next snapshot within the range. If the for loop 804 considers every snapshot within the range and is unable to find a matching entry 806 with a genesis snapshot ID less than the snapshot ID of the relevant version 807, the for loop 804 ends 808. Thus, the process returns an indication that the target file or directory was not found 812.

While FIG. 10 illustrates one embodiment of a directory operation 800, it is recognized that other embodiments may be used. For example, the inputs and outputs may be passed as values, references, and/or stores in an accessible memory location.

X. Read Directory

FIG. 11 illustrates one embodiment of a flowchart of operations for performing a read directory operation 900 on a version of a directory governed by a snapshot. In the depicted embodiment, the read directory operation returns one entry (such as, a file or a directory) located in a version (or, “relevant version”) of a directory (or, “relevant directory”) each time it is executed. It will be appreciated by one with ordinary skill in the art that the depicted embodiment may be modified to return some or all of the entries located within the relevant version of the relevant directory.

Because the depicted embodiment, returns only one entry from the relevant version at a time, an index is used. The index serves as a bookmark that indicates which entry in the relevant version the read directory operation returned last. In the depicted embodiment, the bookmark is implemented using a variable named NEXT INDEX. In one embodiment, NEXT INDEX is the key of the directory entry in the B-tree structure of the relevant directory. It will be appreciated by one with skill in the art that the key is a value that is a identifier of the entry that is unique to at least one of a file system, a B-tree, a storage node, and a storage device. Accordingly, NEXT NAME is the name of the entry that has a key equal to NEXT INDEX.

Additionally, because the read directory operation 900 returns one entry at a time, the process returns an entry in response to an index value, PREVIOUS INDEX, that corresponds to the key of the last entry returned by the operation. The use of PREVIOUS INDEX helps insure that process 900 does not return entries that were previously returned. Thus, process 900 is a function of PREVIOUS INDEX.

The process 900 begins 901 by receiving the snapshot ID of the relevant snapshot 902. Then, the process gets all snapshots with snapshot IDs greater than or equal to the snapshot ID of the relevant snapshot 903. In one embodiment, the process retrieves this range of snapshots because entries for a particular version of a directory are stored either as an entry in that directory version or in subsequent versions. Thus, the process looks at the relevant version or look ahead to retrieve entries located within the relevant version. After the inodes are retrieved 903, the process creates the variable NEXT NAME, and the variable NEXT INDEX, initializing it to a value of MAX_INT 904.

Then, a for loop 905 considers each of the retrieved inodes. Next, a nested for loop 906 considers each entry in the version considered by for loop 905, starting at a location in the relevant directory corresponding to PREVIOUS INDEX+1.

Decision block 907 asks whether the index of the considered entry is greater than NEXT INDEX. For the first entry considered, the index of the entry will not be greater than NEXT INDEX because NEXT INDEX is initialized to MAX_INT. However, for subsequent considered entries, if the index of the entry is greater than NEXT INDEX, the for loop 906 breaks 908 and the next version of the relevant directory is considered 905.

If the index of the considered entry is not greater than NEXT INDEX 907, decision block 909 asks whether the genesis snapshot ID of the entry is less than or equal to the snapshot ID of the relevant version. If it is not, the next entry in the version is considered 906.

However, if the genesis snapshot ID of the considered entry is less than or equal to the snapshot ID of the relevant version, the entry was created before the relevant version and is, therefore, a child of the relevant version of the relevant directory. Thus, NEXT NAME is assigned a value that corresponds to the name of the considered entry, and NEXT INDEX is assigned a value that corresponds to the index of the entry 910. Next, for loop 906 breaks 911 and the next inode version is considered 905. However, if all of the entries in the considered version have neither an entry index greater than NEXT INDEX 907 nor a genesis snapshot ID less than or equal to the snapshot ID of the relevant version 909, for loop 906 ends 912 and the next version is considered 905.

Even if the operation of block 910 executes in a previous iteration of for loop 905, the next version is considered because there could exist an entry that has an index that is greater than PREVIOUS INDEX+1 but less than the present value of NEXT INDEX. After all versions of the relevant directory within the range have been considered, for loop 905 ends 913. Next, decision block 914 asks whether NEXT NAME stores a value. If it does store a value, an entry within the relevant version with an index greater than PREVIOUS INDEX was found, and the process returns NEXT NAME and NEXT INDEX 916. However, if NEXT NAME does not store a value, no entry in the relevant version with an index greater than PREVIOUS INDEX was found, and the process returns “NO MORE ENTRIES EXIST” 915.

While FIG. 11 illustrates one embodiment of a directory operation 900, it is recognized that other embodiments may be used. For example, all entries may be returned by recursively calling operations 905-916 and reassigning PREVIOUS INDEX to equal NEXT INDEX, each time the operations 905-916 are called. Additionally, the inputs and outputs may be passed as values, references, and/or stores in an accessible memory location.

XI. File Structure Implementations

In the embodiment discussed above, inodes associated with files reference BADDR locations in a metatree that store either real BADDR records or ditto records which reference the next version of the file. For ease of reference, this file structure implementation will be referred to as the logical model. However, it is recognized that other file structure implementations exist, such as, for example, a physical model, a hybrid model and a log-based model. Each of these models is described in detail below.

A. Logical Model

FIG. 12A illustrates one embodiment of a logical model file structure implementation. The logical model utilizes an inode/metatree pair for the current version of the file and an inode/metatree pair for each snapshot version of the file. Metatree 1022 represents the current version of a file and metatree 1020 represents a snapshot version of the file. The current version stores records for all BADDR locations in the metatree that point to the physical disk 1024. Thus, the BADDR addresses corresponding to locations 1001 reference data blocks 1004, BADDR locations 1002 reference data blocks 1005, and BADDR locations 1003 reference data blocks 1006.

The snapshot version of the file only references data blocks on the physical disk 1024 that have been modified and thereby COWed since the snapshot was created. Accordingly, because BADDR locations 1002 were modified, BADDR locations 1010 reference data blocks 1007. The remaining BADDR locations in the snapshot version 1009, 1011 include ditto records which reference the next-most recent version 1022. Accordingly, ditto records such as 1009 and 1011 can represent large amounts of data by acting as a compact place-holder.

B. Physical Model

FIG. 12B illustrates one embodiment of a physical model file structure implementation. The physical model utilizes an inode/metatree pair for the current version of the file and an inode/metatree pair for each snapshot version of the file. The current version stores records for all BADDR locations in the metatree that point to the physical disk 1054. Thus, the BADDR addresses corresponding to locations 1036 reference data blocks 1031, BADDR locations 1037 reference data blocks 1032, and BADDR locations 1038 reference data blocks 1033.

The snapshot version 1050 of the file references data blocks in the same way that the current version 1052 references data blocks. BADDR locations 1039 references the same data blocks 1031 as BADDR locations 1036 because the data was not modified after the snapshot was created, and BADDR locations 1041 similarly reference the same data blocks 1033 as BADDR locations 1038. However, BADDR locations 1040 reference different data blocks than BADDR locations 1037 because this portion of the file was modified and consequently COWed. Accordingly, BADDR locations 1040 reference data blocks 1034.

The physical model offers identical snapshot version and current version read times because real BADDR locations are stored in all BADDR locations of the snapshot version. That is, the indirection of the physical model is not present. However, the physical model may be less desirable than the logical model because unchanged portions of the metatree cannot be compactly stored using ditto records.

C. Hybrid Model

FIG. 12C illustrates one embodiment of a hybrid model file structure implementation. In the hybrid model, the current version and all snap shot versions are stored in a single inode/metatree pair. BADDR locations 1.065, 1066, and 1067 represent the current version. Accordingly, BADDR locations 1065, 1066 and 1067 reference data blocks 1061, 1062 and 1063, respectively, and BADDR locations 1068, 1069 and 1070 represent a snapshot version. Because the data in BADDR locations 1065 was not modified after the snapshot was created, BADDR locations 1068 reference BADDR locations 1065 of the current version. Similarly, BADDR locations 1070 references BADDR locations 1067 of the current version. However, because the data in BADDR locations 1066 was modified after the snapshot was created, BADDR locations 1070 references data blocks 1064.

The hybrid model may be more desirable than the logical model when a large number of snapshots have been modified frequently because the indirection in between data structured in the logical model may slow down read operations. However, lookups for delete snapshot operations in a potentially large metatree of the hybrid model may be computationally expensive.

D. Log-Based Model

FIG. 12D illustrates one embodiment of a log-based model file structure implementation. In the log-based model, the current version of a file is stored in an inode/metatree pair 1092 that references the physical disk 1094. Portions of the file that have been modified are COWed to a log 1090 that is referenced by the metatree associated with the current version 1092. Thus, BADDR locations 1088 stored COWed data because data in BADDR locations 1086 have been modified. Reading snapshot data under the log-based model can be performed by reconstructing versions of the file by accessing both the log and the current version of the file. For example, in the depicted embodiment, reading the snapshot data would require accessing BADDR locations 1085, 1088 and 1087.

The log-based model may be more desirable than the other models because snapshot data can be stored compactly, permitting tracking of even single-byte modifications. However, the log-based model may be less desirable than the other models because read operations are more computationally expensive.

XII. Exemplary Applications

FIGS. 13A-D and FIGS. 14A-D provide examples of operations in a file system that implements one embodiment of the snapshot disclosed herein. It is recognized that, though considered, not all possible operations are discussed.

A. File Operations

FIG. 13A illustrates one embodiment of a file. The depicted inode/metatree pair corresponds to the current version of a file that is governed by a snapshot. The inode 500 comprises fields corresponding to the mode 501, LIN 502, and the governance list 503. The node 500 points to the metatree associated with the file 504. The metatree is comprised of BADDR locations that reference blocks on the physical disk.

Before the snapshot governed the file, the governance list of the file stored an empty set, indicating that no snapshots govern the file. Reference to FIG. 6, illustrates the creation of the snapshot of the file shown in FIG. 12A. The process received the path of the file 402 as the root of the snapshot. Next, a snapshot tracking data structure (not shown in FIG. 12A) was created that corresponds to the snapshot taken of the file 403. The global count at the time the snapshot was created is added to the snapshot tracking data structure 404. This value is the snapshot ID. In this example, the snapshot ID is 499.

Because the file is not the root of the file system, a mini-snapshot is created for each of the ancestors of the file to the root of the file system 406, 407, 408. Next, the snapshot ID is added to the governance list of the inode associated with the current version of the file 409. Thus, though the governance list of the snapshot was formerly an empty set, the snapshot of the file is created once the snapshot ID, 499, is added to the governance list 503 of the file's inode 500.

Additionally, the LIN table 505 includes an entry 506 that references the current version of the file. The entry 506 indicates the LIN of the file, 9000, and the genesis snapshot ID of the inode, MAX_INT. MAX_INT is used to indicate that the entry 506 references the most current version of the file. In the depicted embodiment, the LIN table 505 does not include an entry for snapshot ID 499, either before or after snapshot creation, because the current version was not modified after the snapshot was created. In this embodiment, if a user or client application wishes to access snapshot 499, a lookup in the LIN will reveal no entry for snapshot 499 and consequently, the inode with the next highest snapshot ID, MAX_INT, is accessed. In other embodiments, the LIN table 505 may include an entry with LIN 9000 and genesis snapshot ID 499 that references the current version of the file. In other words, there would be two entries in the LIN table 505 that reference the same inode.

FIG. 13B illustrates the embodiment of FIG. 12A after two operations have been executed: a second snapshot of the file was created, and then, a portion of the file was modified.

When the second snapshot was created, process 400 of FIG. 6 was executed in a similar manner as described above with respect to snapshot 499. For this snapshot, the global count was 500 at the time the second snapshot was created. Therefore, the governance list of the inode associated with the current version listed snapshot IDs 499 and 500. Immediately after snapshot 500 was created, the LIN table did not change. Thus, a lookup for snapshot ID 500 would yield no match and the next highest snapshot ID, MAX_INT, would be accessed.

Next, the data associated with BADDR locations 300-600 505 in the current version were modified. Reference to FIG. 7A illustrates the relevant operations for modifying the current version of the file. The process begins 601 by calling the painting process 602 depicted in FIG. 7B. In the painting process 602, decision block 621 asks whether the snapshot ID of the target file/dir is less than the global count. Because we assume that the global count is 500, the snapshot ID, 500, is equal to the global count. Thus, the operations of the painting process 602 are not required and process 602 ends 636.

Next, decision block 603 asks whether the file is governed by a snapshot. The governance list of the current version indicates that both snapshots 499 and 500 govern the current version of the file. Thus, the create snapshot version of file/dir process 604 is called. First, the LIN of the file, 9000 is added to the tracking file of the governing snapshot (not shown) 611. Next, the inode of the file is copied 612. The copy of the inode is represented by data structure 510 in FIG. 13B. Accordingly, the inodes of the current version 500 and snapshot version 510 differ in that the snapshot version is governed by snapshot IDs 499 and 500 whereas, the current version is no longer governed by a snapshot. Finally, the LIN of the snapshot version is added to the LIN table 550. As depicted, LIN 9000 with snapshot ID 500 is added to the LIN table. Notably, snapshot ID 499 does not have to be added to the LIN table because snapshots 499 and 500 reference the same metatree locations.

Then, decision block 606 asks whether a file or a directory is being modified. Because a file is being modified, the file COW process 605 of FIG. 7D is called. The file COW process first asks whether a previous version of a file exists 641. In this example, previous versions corresponding to snapshot IDs 499 and 500 exist. Thus, decision block 642 asks whether there is a ditto record for the BADDR locations to be modified in the previous version. Because there have been no previous modifications to the file, all BADDR locations in the previous version include a ditto record. Thus, the ditto record from BADDR locations 300-600 in the snapshot version are removed 644 and the original data from BADDR locations 300-600 in the current version are copied to BADDR locations 300-600 in the snapshot version 645. Next, the BADDR locations 300-600 in the current version can be modified 646. Thus, the snapshot version includes ditto records for BADDR locations 0-300 514 and 601-1000 516. BADDR locations 300-600 515 includes references to the portion of the physical disk that stores the COWed data.

FIG. 13C illustrates an extension of the preceding example. The embodiment depicted shows the data structures associated with the snapshot versions 510, 520 and the current version 500 after the execution of two operations: a new snapshot was created, and then, the current version of the file was modified.

As discussed above with respect to FIGS. 13A and 13B, the snapshot creation process 400, adds the snapshot ID of the snapshot to the governance list of the current version 503. Assuming that the global snapshot count at the time the snapshot is taken is 501, snapshot ID 501 is added to the governance list of the current version and a snapshot tracking file associated with snapshot 501 (not shown) is created.

Next, a user or client application wishes to modify the data associated with BADDR locations 0-100 504 in the current version. Assuming that the global count is 501, the painting process 602 is bypassed because the snapshot ID, 501, is equal to the global count 621. Next, the LIN is added to the snapshot tracking file associated with snapshot 501 611, the inode of the current version is copied 612 so as to correspond to snapshot 501 520, and the new inode is added to the LIN table 613. As shown, the LIN table 550 includes new row 553 with the LIN/snapshot ID pair (9000, 501). This row 553 points to the inode associated with snapshot 501 520.

Next, because a file is being modified, the file COW process 605 is called. Because there exists a previous version of the file 641 with a ditto record in the BADDR locations to be modified 524, the data in BADDR locations 0-100 504 from the current version are copied to BADDR locations 0-100 524 of snapshot 501. Next, the data associated with BADDR locations 0-100 504 in the current version may be modified. Thus, in snapshot 501, BADDR locations 0-100 524 include a reference to the physical disk, and BADDR locations 101-1000 524 include ditto records.

Notably, in order to modify the current version governed by snapshot 501, changes to the metatrees associated with snapshot IDs 499 and 500 510 are not required. Therefore, snapshot version 500 is read in the following way: for BADDR locations 0-100, the ditto record references version 501 which includes references to the physical disk; for BADDR locations 101-300, ditto records in version 500 and 501 reference the current version which includes references to the physical disk; BADDR locations 301-600 include direct references to the physical disk; and for BADDR locations 601-1000, ditto records in version 500 and 501 reference the current version which includes references to the physical disk. Therefore, to read the entire contents of version 500, the metatrees for version 500, version 501 and the current version need to be accessed.

FIG. 13D illustrates an extension of the preceding example. The embodiment depicted shows the deletion of snapshot 501. Reference to FIG. 8 illustrates the operations executed in order to delete snapshot 501. After the delete snapshot request is accepted 482, for loop 483 considers each file or directory in the snapshot tracking file of snapshot 501. In this example, the root of the snapshot is a file that has no children. Therefore, the only entry in the snapshot tracking file of snapshot 501 corresponds to LIN 9000. Therefore, the operations in for loop 483 will execute only once. Decision block 484 asks whether there is a previous version of the file. Because snapshots 499 and 500 are previous versions of the file, the process proceeds to decision block 485 which determines that a file is under consideration. Next, the data from the snapshot to be deleted is copied to a previous version of the file. In the example, snapshot 501 stored real BADDR records only in locations 0-100. Therefore, only these records need to be copied to the same locations in the metatree 517 for snapshot 500.

Then, the inode and metatree associated with version 501 520 can be deleted 492, and the reference 553 in the LIN table to snapshot 501 can be deleted 493. In other embodiments, the entire row in the LIN table may be deleted. Because only one file was under consideration, for loop 483 ends 490 and the snapshot tracking file associated with snapshot 501 is deleted.

After the deletion of snapshot 501, a read operation on version 500 proceeds in the following manner. First, the inode of the file is received and each BADDR location in the region being read is considered. For locations 0-100 517, data can be accessed by performing a lookup of the BADDR locations on the physical disk 708 because a real BADDR record exists 706 for these locations. However, for BADDR locations 101-300 518, the next inode version needs to be read to find a real BADDR record. Thus, a lookup on the physical disk relies on real BADDR records 508. Similarly, a read on BADDR locations 301-600 515 occurs in a similar way to BADDR locations 0-100 517 because a real BADDR record exists. A read on BADDR locations 601-1000 516 occurs in a similar way to BADDR locations 101-300 518 because a ditto record exists.

B. Directory Operations

FIG. 14A illustrates one embodiment of a directory, dir2/, governed by snapshot 602. When the directory was created, the inode 560 included an empty set in its governance list 563. The metatree for dir2/ includes entries 564, 565, 566 associated with its child inodes. For example, file4 with LIN 5001 was added when the global snapshot count was 597; dir3/ with LIN 5002 was added when the global snapshot count was 596; and file5 with LIN 5003 was added when the global snapshot count was 601. Note the deviation from the example file hierarchy in FIG. 2A (such as, in FIG. 14A, file5 is a child of dir2/).

Assuming the global snapshot count is 602 at the time the first snapshot of dir2/ is created, creation of a snapshot with a root of dir2/ first creates a snapshot tracking file 403 and adding snapshot ID 602 to the snapshot tracking file 404. Then, a mini-snapshot for each parent of dir2/ to the root is created 406, 407, 408 because dir2/ is not the root of the file system 405. Next, snapshot ID 602 is added 409 to the governance list 563 of the current version of dir2/ 409.

FIG. 14B illustrates an extension of the preceding example. The depicted embodiment shows the inode/metatree pair 570 associated with snapshot 602 and the inode/metatree 560 pair associated with the current version after file4 has been deleted from the current version. FIG. 7A provides one embodiment of the operations for deleting file4 from the current version. First, assuming the global snapshot count is 602, the painting process 602 is skipped because the snapshot ID, 602, is equal to the global snapshot count 621. Next, a snapshot version of dir2/ is created by the create snapshot version of file/dir process 604. Process 604 adds the LIN of file4, 5001, to the snapshot tracking file 611 associated with snapshot 602; makes a copy of the inode of the current version 612; and adds the LIN/snapshot ID pair, (5000, 602) to the LIN table (not shown). Notably, when the inode is copied, the governance list of the snapshot version 573 is 602, and the governance list of the current version 563 includes an empty set.

Then, the directory COW process 607 is executed because a file included in dir2/ is being modified. When removing an entry 651, the directory COW process asks 654 whether the genesis snapshot ID of file4 is more recent than the snapshot 602. Because the genesis snapshot ID of file4 is 597 and the governing snapshot ID is 602, the entry for file4 is copied 655 to the same key location 574 in the metatree for snapshot 602. Next, file4 is removed from the current version 655. Generally, after a file is modified, the genesis snapshot ID of the file in the current version is set to the global snapshot count 657. However, in this example, the genesis snapshot ID for file4 is not set to the global snapshot count because file4 was deleted from the current version.

FIG. 14C illustrates an extension of the preceding example. The illustrated embodiment shows the inodes/metatree pairs associated with snapshot 602 570, snapshot 603 580 and the current version 560 after the following operations have executed in the recited order: (1) a snapshot was created when the global count was 603, (2) file5 was modified when the goal snapshot count was 604, and (3) file6 was added when the global snapshot count was 604.

As discussed above with respect to FIGS. 14A and 14B, snapshot 603 is created by adding snapshot ID 603 to the governance list of the current version. Additionally, a snapshot tracking file with snapshot ID 603 is created. Then, when a request to modify file5 is accepted, the inode of the current version is copied. The copied inode 580 includes the snapshot ID 603 in its governance list 583, and the governance list of the current version 563 includes an empty set. Before file5 can be modified, it is copied to snapshot 603 because its snapshot ID is greater than genesis snapshot ID 601 of file5. After the COW 655 is complete, file5 is modified in the current version 656. Accordingly, the genesis snapshot ID of file5 in the current version 568 is set to global count 604, indicating when file5 was last modified.

Next, file6 with LIN 5004 is added to dir2/ when the global count was 604. FIG. 7E illustrates how an entry may be added to a directory governed by a snapshot. First, the entry is added to the metatree associated with the inode of the current version 652. Then, in the LIN table, the snapshot ID for the entry is the same as the snapshot ID of the current version 653. Also, the genesis snapshot ID of file6 569 in the metatree of the current version of dir2/ is set to the global count.

In order to perform a lookup operation for a particular file or directory in a particular version of dir2/, the directory lookup process 800 first receives the target file or directory and the LIN/snapshot ID pair of the relevant directory 803. For example, assume that the target file or directory is file5 and that the lookup operation is directed to the version 602 of dir2/, snapshot ID pair (5000, 602).

For loop 804 first examines snapshot 602 and determines that there is no matching entry in the local portion of the tree 806. Next, snapshot 603 is considered. A matching entry for file5 exists in the local portion of the tree 806. Thus, to determine if the matching entry was included in the current version of dir2/, decision block 807 asks whether the snapshot ID is less than the snapshot ID of the relevant version. Here, the snapshot ID for file5 in snapshot 603 is 601, and the snapshot ID of the relevant version is 602. Therefore, the for loop breaks 809 and the location and/or the path of file5 with genesis snapshot ID 601 is returned.

In order to perform a read directory operation for a particular version of dir2/, the read directory process 900 first receives the inodes for the snapshot versions that have snapshot IDs greater than the snapshot ID of the relevant version. For example, assume that the read directory operation is directed to snapshot 603 of the dir2/. Accordingly, the inodes for snapshot 603 and the current version are received. To retrieve each entry in version 603 of dir2/, the read directory operation examines each entry 906 in each received inode version 905. If the genesis snapshot ID of the considered entry is less than or equal to the snapshot ID of the relevant version 909, the process returns the name of the entry 916. However, if the snapshot ID of the entry is greater than the snapshot ID of the relevant entry, the process considers the next entry 911.

In the illustrated example, the process first considers file5 in version 603. It is returned as an entry in this version of dir2/ because its snapshot ID, 601, is less than the relevant snapshot ID, 603. Similarly, the snapshot ID of each entry in the current version is considered. Therefore, dir3/ is the only entry returned because the entries for file5 and file6 each have snapshot IDs greater than the snapshot ID of the relevant version. Thus, a read directory operation for the entire contents of snapshot version 603 of dir2/ would indicate that dir2/ includes file5 (with genesis snapshot ID 601) and dir3/ (with genesis snapshot ID 598).

FIG. 14D illustrates an extension of the preceding example. In the depicted embodiment, the metatrees associated with snapshot 602 570 and the current version 560 are shown after snapshot 603 has been deleted. In order to delete snapshot 603, each file or directory in the snapshot tracking file for snapshot 603 is visited 483. Here, the only file in the snapshot tracking file for snapshot 603 is file5 with genesis snapshot ID 601. Thus, because a previous version, snapshot 602, of dir2/ exists and file5 is a file, the entry in snapshot 603 is copied to snapshot 602. Then, the inode and metatree for snapshot version 603 of file5 is deleted 492, and the entry associated with the LIN/snapshot ID pair (5003, 603) is deleted from the LIN table 493. Afterward, the snapshot tracking file, inode and metatree associated with snapshot 603 of dir2/ are deleted 494.

XIII. Adaptive Copy-On-Write

As described above with respect to FIGS. 7D and 7E, in some embodiments, data associated with a modified file or directory is COWed. In other words, data from the current version of the file or directory is copied, using a COW process, before permitting the modification of the current version. As described in greater detail below, data may also be copied using a Point-In-Time-Copy (PITC) process. In some circumstances, it may be more advantageous to use PITC, rather than COW. Some embodiments, therefore, implement adaptive COW, choosing, based on the type of modification and/or other factors, whether to use COW, PITC, or a combination of both.

FIGS. 15A and 15B illustrate different embodiments of storing a single file in a distributed manner across a cluster of computer nodes 1500. In FIG. 15A, a 512 kilobyte (kB) file is processed at the Client Application Layer 1502. In the Coalescer Layer 1504, a file is divided into 128 kB portions. In the illustrated embodiment, 128 kB of parity information are stored for every two 128 kB portions of the file. The illustrated Coalescer Layer 1504 determines the parity information for the two 128 kB file portions. Then, at the Storage Layer 1506, the two 128 kB file portions and the associated 128 kB parity information are stored on a respective node of the cluster of computer nodes 1500.

FIG. 15B illustrates another embodiment in which files on the cluster of computer nodes 1500 are processed only at Client Application Layer 1502 and Storage Layer 1506. In this embodiment, the data blocks of a 512 kB file are divided into a smallest unit of storage and stored accordingly, without coalescing blocks into block clusters, such as 128 kB portions, and without determining or storing any parity data. One skilled in the art will appreciate that there are many suitable ways to store portions of a file in a file system, such as a distributed file system implemented for a cluster of computer nodes 1500. Although illustrated and described in terms of a distributed file system, the embodiments described herein are not limited to a distributed file system.

COW and PITC

FIGS. 16A and 16B illustrate flowcharts of respective embodiments of a COW process and a PITC process. FIG. 16A illustrates a flowchart of one embodiment of instructions executing a COW process 1600. The instructions may be stored in a module, such as, for example, the snapshot module 113, and executed on a processor. The COW process 1600 executes the states between 1602 and 1610 for the data blocks being modified by the COW process 1600. In state 1604, the COW process 1600 allocates a new data block and assigns it to the relevant snapshot version of the file. In state 1606, the COW process reads the value from the corresponding data block of the current version of the file. In state 1608, the COW process writes the value read from the current version of the file to the new allocated data block.

FIG. 16B illustrates a flowchart of one embodiment of instructions executing a PITC process 1612. The instructions may be stored in a module and executed on a processor. The PITC 1612 process executes the states between 1614 and 1620 for the data blocks being modified by the PITC process 1612. In state 1616, the PITC process 1612 allocates a new data block and assigns it to the current version of the file. In state 1618, the PITC process 1612 transfers a corresponding data block from the current version of the file to the relevant snapshot version of the file.

B. Example Snapshots

For purposes of illustration only, the embodiments described herein include file systems that write data contiguously in sixteen-block clusters (with 8 kB data blocks)—in other words, in groups of 128 kB. For example, the 512 kB file described above, with reference to FIG. 15A, is divided into four 128 kB portions. These portions are grouped together in groups of two, and corresponding parity data (128 kB) is created for each pair. The sixteen-block cluster pairs and their respective parity data are stored on respective nodes of the cluster of computer nodes 1500. Each respective sixteen-block cluster, including the parity data, is written in contiguous physical address space. One skilled in the art will appreciate that there are many suitable cluster sizes for writing contiguous data, including, for example, one block, four blocks, five blocks, sixteen blocks, one-hundred and thirty-five blocks, one-thousand blocks, and so forth. One skilled in the art will also appreciate that there are many suitable block sizes including, for example, 1 kB, 4 kB, 5 kB, 128 kB, 1 megabyte, and so forth.

In the examples described below, reference is made to metatrees 1700, BADDRs 1704, and physical storage 1706. In the illustrated embodiments, metatrees 1700 correspond to different versions of a file, such as the current version of a file or various snapshot versions of the same file. Metatrees 1700 include BADDRs 1704, which are the instructions for finding the various data blocks that comprise a given version of a file. BADDRs 1704 store, in the illustrated embodiments, either a physical address or a ditto record. The physical addresses are addresses to data blocks of physical storage 1706. Physical storage 1706 may be any suitable storage device, including a hard-disk drive, heterogeneous or homogeneous arrays of drives, random access memory (RAM), flash storage, and so forth. As described above with reference to FIGS. 7D and 7E, ditto records indicate that a BADDR references another BADDR in the next version of the file. A ditto record instructs the file system to look at the corresponding BADDR in the next version of the file system (the next metatree 1700), which may either include a physical address or another ditto record, directing the file system to look at the corresponding place in the next version of the file (the next metatree 1700), and so forth. In some embodiments, a ditto record may comprise a flag value that indicates that the file system should look for the address in the corresponding BADDR in the data structure of the next version of the file. In other embodiments, a ditto record may be an address, for example, to a data structure of the next version of the file. As used herein, the next version of the file refers to next most current version.

1. Example COW

FIGS. 17A-1, 17A-2, and 17A-3 illustrate an embodiment showing portions of the current version of a 16 kB file that are copied using copy-on-write (COW) to a snapshot version of the file prior to being overwritten. FIG. 17A-1 illustrates the current version and a snapshot version of a 16 kB file both before and after a partial overwrite. Prior to the overwrite, the current version and the snapshot version of the file are identical. Thus, the current version and the snapshot version both include data blocks 100 and 101, stored contiguously on physical storage 1706. Accordingly, the snapshot metatree[5004,497] 1700, which corresponds to snapshot one 221, has BADDRs 1704 with ditto records referencing the corresponding BADDRs 1704 in the current metatree[5004,−1] 1700, which corresponds to the current version of the file.

The partial overwrite only overwrites the first data block 100 (0 to 7 kB). To perform a COW, a new data block 300 is allocated in physical storage 1706 to store the value of the data block being overwritten. The contents of data block 100 are then copied to data block 300. The BADDR[0] 1704 of snapshot metatree[5004,497] 1700 is assigned the address of data block 300. After the overwrite, the current version of the file still includes data blocks 100 and 101, and the snapshot version includes data blocks 300 and 101. The snapshot metatree[5004,497] 1700 includes BADDR[0] 1704 to the newly allocated data block 300 and a BADDR[1] 1704 with a ditto record pointing to the BADDR[1] 1704 in the current metatree[5004,−1] 1700.

FIG. 17A-2 illustrates adding another snapshot version of the 16 kB file illustrated in FIG. 17A-1. A new snapshot version corresponding to snapid of “720” (snapshot three 223) is created for the file corresponding to LIN 5004. Prior to a modification of the current version of the file, the new snapshot version (snapid of “720”) of the file is identical to the current version of the file. Thus, the new snapshot version (snapid of “720”) and the current version of the file both include data blocks 100 and 101. Accordingly, snapshot metatree[5004,720] 1700 includes BADDRs with ditto records referencing corresponding BADDRs in the current metatree[5004,−1] 1700. Because the current version of the file has been modified since the creation of the previous snapshot version (snapid of “497”), the current version of the file and the previous snapshot version (snapid of “497”) of the file are different. The previous snapshot version (snapid of “497”) includes data blocks 300 and 101. Accordingly, snapshot metatree[5004,497] 1700 includes a BADDR[0] with the address of data block 300 and a BADDR[1] with a ditto record pointing to the corresponding BADDR[1] 1704 in the snapshot metatree[5004,720] 1700, which includes a ditto record pointing to BADDR[1] 1704 in the current metatree [5004, −1] 1700.

FIG. 17A-3 illustrates copying with COW a data block of the 16 kB file modified in FIG. 17A-1, including the new snapshot, as illustrated in FIG. 17A-2. During the COW, a new data block 500 is allocated in physical storage 1706, and the contents of data block 101 are copied to newly allocated data block 500. The BADDR[1] 1704 in snapshot metatree[5004,720] 1700 is assigned the address of the newly allocated data block 500. The new snapshot version (snapid of “720”) of the file now includes data blocks 100 and 500. The snapshot metatree[5004,720] 1700 still includes a BADDR[0] 1704 referencing the corresponding BADDR[0] 1704 in the current metatree[5004,−1] 1704. The snapshot metatree[5004,497] 1700 remains unchanged. It includes a BADDR[0] 1704 with the block address of data block 300. It also includes a BADDR[1] 1704 referencing the BADDR[1] 1704 in the snapshot metatree [5004,720] 1700. The current version of the file still includes data blocks 100 and 101. The current metatree[5004,−1] 1700 includes BADDRs pointing to the addresses of data blocks 100 and 101, respectively.

2. Example PITC

FIGS. 17B-1, 17B-2 and 17B-3 illustrate copying a data block using a point-in-time-copy (PITC). FIG. 16B-1 illustrates a snapshot version (snapshot one 221) and the current version of a 16 kB both before and after one of its data blocks is overwritten. Prior to the overwrite, the snapshot version and the current version are the same. Thus, the current version and the snapshot version of the file both include data blocks 100 and 101, stored contiguously on physical storage 1706. Accordingly, snapshot metatree[5004,497] 1700 includes BADDRs with ditto records referencing the respective BADDRs in the current metatree[5004,−1] 1700.

To perform a PITC, the copied block, data block 100, is transferred from the current version of the file to the snapshot version of the file. Accordingly, the value of BADDR[0] 1704 of the current metatree[5004,−1] 1700, which is the address of data block 100, is transferred to the snapshot metatree[5004,497] 1700. A new data block, data block 300, is then allocated in physical storage 1706 and written with the overwrite value. The BADDR[0] 1704 of current metatree[5004,−1] 1700 is now assigned the address of data block 300. After the PITC, the current version of the file includes data blocks 300 and 101, and the snapshot version of the file includes data blocks 100 and 101. The snapshot metatree [5004,497] 1700 now includes BADDR[0] 1704 with the address of data block 100 and still includes BADDR[1] 1704 with a ditto record referencing BADDR[1] 1704 in current metatree[5004,−1] 1700. The current metatree[5004,−1] 1700 now includes BADDR[0] with the address of data block 300 and still includes BADDR[1] 1704 with the address of data block 101.

FIG. 16B-2 illustrates adding another snapshot version of the 16 kB file modified as illustrated in FIG. 16B-1. A new snapshot version corresponding to snapid of “720” (snapshot three 223) is created for the file corresponding to LIN 5004. Following the creation of the new snapshot version (snapid of “720”), and prior to any modification of the current version of the file), the new snapshot version (snapid of “720”) and the current version of the file are identical. Thus, the new snapshot version (snapid of “720”) and the current version of the file include data blocks 300 and 101. Accordingly, snapshot metatree[5004,720] 1700 includes BADDRs with ditto records referencing corresponding BADDRs in the current metatree[5004,−1] 1700. Because the current version of the file was modified previously, the previous snapshot version (snapid of “497”) of the file includes data blocks 100 and 101. Accordingly, snapshot metatree[5004,497] 1700 includes a BADDR[0] with the address of data block 100 and a BADDR[1] with a ditto record pointing to the corresponding BADDR[1] 1704 in the snapshot metatree[5004,720] 1700, which includes a ditto record pointing to BADDR[1] 1704 in the current metatree [5004, −1] 1700.

FIG. 16B-3 illustrates using PITC for a partial overwrite of the 16 kB file, as described above with respect to FIG. 16B-1, to which an additional snapshot was added, as described with respect to FIG. 16B-2. To perform the PITC, data block 101 is transferred from the current version of the file to the new snapshot version (snapid of “720”) of the file. Specifically, the value of block address 101 stored in BADDR[1] of current metatree[5004,−1] 1700 is transferred to BADDR[1] of snapshot metatree[5004,720]. A new data block, data block 301, is then allocated in physical storage 1706 and written with the overwrite value. Thus, following the PITC, the current version of the file includes contiguous data blocks 300 and 301; the new snapshot version (snapid of “720”) includes data blocks 300 and 101; and the previous snapshot version (snapid of “497”) of the file includes data blocks 100 and 101. The BADDR[1] of current metatree[5004,−1] is then assigned the address of newly allocated data block 301. Thus, after the PITC, the current metatree[5004,−1] 1700 includes BADDRs 1704 with the addresses of data blocks 300 and 301. The snapshot metatree[5004,720] 1700 still includes BADDR[0] 1704 with a ditto record pointing to BADDR[0] 1704 in the current meta-tree[5004,−1] 1700 and now includes BADDR[1] 1704 with the address of data block 101. The snapshot metatree[5004,497] 1700 still includes BADDR[0] 1704 with the address of data block 100 and still includes BADDR[1] 1704 with a ditto record pointing to BADDR[1] 1704 in snapshot metatree[5004, 720] 1700.

C. Adaptive COW

Although COW and PITC achieve the same functionality, saving a copy of the original data in a snapshot version before allowing the current version to be modified, COW and PITC have distinct advantages and disadvantages. With respect to COW, the main advantage is that the layout of the current version of the file is unaffected, as described above with respect to FIGS. 17A-1, 17A-2, and 17A-3. In other words, the contiguous data blocks allocated when the file was created are kept intact, allowing them to be read more quickly than if the blocks were non-contiguous. In contrast, the PITC process is faster to execute, but does not preserve the contiguous layout of the current version of the file, as described above with respect to FIGS. 17B-1, 17B-2, and 17B-3. Because it may be more advantageous, in some circumstances, to use PITC, rather than COW, some embodiments implement adaptive COW, choosing, based on certain factors, whether to use COW, PITC, or a combination of both.

1. Flowchart

FIGS. 18A and 18B illustrate flowcharts of one embodiment of instructions executing an adaptive COW process 1800. The instructions may be stored in a module, such as, for example, the snapshot module 113, and executed on a processor. In state 1802, the adaptive COW process 1800 receives a request to modify a file for which a snapshot was previously requested. In state 1804, the adaptive COW process 1800 determines whether to perform a PITC or a COW operation and then performs the determined operation. This state is described in greater detail below with reference to FIG. 18B. In state 1806, the adaptive COW process 1800 allows the request to modify the file to continue.

FIG. 18B illustrates one embodiment of state 1804, described above with reference to FIG. 18A. In state 1808, the adaptive COW process 1800 determines whether the entire file is being deleted or overwritten. If the entire file is not being deleted or overwritten, then the adaptive COW process 1800 proceeds to state 1814. If the entire file is being deleted or overwritten, the adaptive COW process 1800 determines, in state 1810, whether any blocks in the file have been COWed previously. If any one of the blocks in the file have been COWed previously, then the adaptive COW process 1800 proceeds to state 1812 and transfers the entire list of block addresses from the current version of the file to the snapshot version. If any of the blocks in the file have been COWed previously, then the adaptive COW process 1800 proceeds to state 1814.

The adaptive COW process 1800 executes the states between 1814 and 1824 for the contiguous portions of the file being deleted or overwritten. In some embodiments, the contiguous portions are sixteen-block clusters of 8 kB blocks—in other words, 128 kB portions of the file—or the remaining portion after a file has been divided into sixteen-block clusters, including an entire file that is less than a sixteen-block cluster (128 kB), though other cluster sizes and/or number of cluster blocks may be used. In state 1816, the adaptive COW process 1800 determines whether the relevant contiguous portion is being entirely deleted or overwritten. The relevant contiguous portion is the contiguous portion of the file that is being operated on during one pass of the loop defined by states 1814 to 1824. If the relevant contiguous portion is not being entirely deleted or overwritten, the adaptive COW process 1800 executes a normal COW operation, in state 1822, as described above with reference to FIG. 16A. If the relevant contiguous portion is being entirely deleted or overwritten, then the adaptive COW process 1800 determines, in state 1818, whether any blocks in the relevant contiguous portion have been COWed previously. If any of the blocks in the relevant contiguous portion have been COWed previously, the adaptive COW process 1800 executes a normal COW, in state 1822, as described in greater detail above with reference to FIG. 16A. If none of the blocks of the relevant contiguous portion have been COWed previously, then the adaptive COW process 1800 uses PITC to transfer the entire relevant contiguous portion, in state 1820, as described in greater detail above with respect to FIG. 16B.

2. Example Operations

FIGS. 19A, 19B, 19C, 19D, 19E, and 19F illustrate various file operations (overwrites and deletions) and the corresponding result of implementing one embodiment of adaptive copy-on-write.

FIG. 19A illustrates an example when the entire file is being overwritten (and no blocks have yet been COWed in the entire file), in which case PITC may be used to transfer the entire list of block addresses from the current version of the file to the snapshot version. Because the PITC operation will not disturb the sixteen-block contiguity, it is possible to use the more efficient PITC instead of COW to achieve faster write speed without the drawback of fragmenting the file. The newly allocated blocks for the current version of the file will be contiguous since they are being allocated at the same time, and the advantages of PITC may be gained without fragmenting the current version.

FIG. 19B illustrates an example when an entire file is being deleted (and no blocks have yet been COWed in the entire file), in which case PITC may be used to transfer the entire list of block addresses from the current version of the file to the snapshot version. Because the current version of the file is no longer needed, the entire list of block addresses may be transferred to the snapshot version of the file.

FIG. 19C illustrates an example when a file is partially overwritten, but there are contiguous subportions of the overwritten portion (which have not been COWed previously), in which case the contiguous subportion may be transferred with PITC, and the remainder of the overwritten portion may be COWed. Because there is a contiguous cluster of sixteen blocks being overwritten (and no blocks within that cluster have yet been COWed), PITC may be used to transfer that contiguous sixteen-block range. The newly allocated blocks in the current version of the file will be contiguous since they are being allocated at the same time, and the advantages of PITC may be gained without fragmenting the current version. The remaining, noncontiguous block is COWed in order to keep contiguity with the neighboring block (136 to 143 kB) that is not overwritten. Using PITC would have caused a new block to be allocated in the current version of the file (the 128 to 135 kB block), which would not be contiguous with the unwritten portion.

FIG. 19D illustrates an example when a file is partially deleted. The partially deleted portion of the file may be copied using PITC because the operation will not disturb the contiguity of the remaining portion of the file. Thus, the advantages of PITC (fast write speed) may be gained without fragmenting the current version of the file.

FIG. 19E illustrates an example when a file is partially overwritten and some portions of the current version of the file are copied into a snapshot version using COW and other portions are copied using PITC. The contiguous cluster of sixteen blocks being overwritten (the blocks spanning the address range of 128 to 255 kB) may be transferred, using PITC, from the current version of the file to the snapshot version of the file. The newly allocated blocks in the current version will be contiguous since they are being allocated at the same time. Thus, the advantages of PITC (fast write speed) may be gained without fragmenting the current version of the file. Again, this is a case when none of the locks in the sixteen-block contiguous portion have been COWed previously. The eight-block cluster spanning address range 64 to 127 kB are COWed because this preserves the contiguity of the sixteen-block cluster spanning the address range of 0 to 127 kB in the current version of the file. Similarly, the block spanning the address range from 256 to 263 kB is also COWed because this preserves the contiguity of the two-block cluster spanning the address range from 256 to 271 kB in the current version of the file.

FIG. 19F illustrates an example when an entire file is overwritten with a larger file. This example is similar to the example illustrated and described in greater detail above with respect to FIG. 19A. Because the newly allocated blocks of the overwritten file will be contiguous, as they are being allocated at the same time, the advantages of PITC may be gained (faster write speed) without fragmenting the current version of the file.

FIGS. 20A, 20B, 20C1, 20C2, 20C3, 20D, 20E1, and 20E2 illustrate in greater detail the file modifications briefly described above with respect to the embodiments shown in FIGS. 19A-19E.

FIG. 20A illustrates an example when an entire file is overwritten (and no blocks in the file have yet been COWed), in which case the entire list of block addresses may be transferred using PITC from the current version of the file to the snapshot version. FIG. 20A illustrates the status of metatrees 1700 and the physical storage 1706 both before and after the entire overwrite of a 16 kB file. In the example illustrated, the file corresponding to LIN 5004 (file6 212) has one snapshot corresponding to it, snapshot three 223 (snapshot ID 720). Prior to the overwrite, the file has not been modified since snapshot three 223 was created. Thus, all of the BADDRs 1704 in the snapshot metatree[5004,720] 1700 contain ditto records, pointing to the corresponding BADDRs 1704 in current metatree[5004,−1]. The BADDRs 1704 in current metatree[5004,−1] 1700 reference the data blocks 100 and 101 stored contiguously in physical storage 1706.

Because the entire file is being overwritten, the adaptive COW process 1800 uses PITC to transfer the block addresses from the current version of the file to the snapshot version of the file. Specifically, the address values of data blocks 100 and 101 stored in the BADDRs 1704 of the current metatree[5004,−1] 1700 are transferred to the corresponding BADDRs 1704 in the snapshot metatree[5004,720] 1700. Two new blocks (data blocks 500 and 501) in physical storage 1706 are then allocated. The BADDRs 1704 in current metastructure[5004,−1] 1700 are then assigned the addresses of the newly allocated data blocks. Thus, the current version of the file includes the contiguous data blocks 500 and 501 on physical storage 1706, and the snapshot version of the file also includes the contiguous data blocks 100 and 101 on physical storage 1706.

FIG. 20B illustrates an example when an entire file is deleted (and none of the blocks in the file have yet been COWed), in which case the adaptive COW process 1800 uses PITC to transfer the entire list of block addresses from the current version of the file to the snapshot version. FIG. 20B illustrates the status of metatrees 1700 and physical storage 1706 both before and after the file is deleted. Before the file is deleted, in this example, none of the data blocks in the file have been modified previously. Hence, the snapshot metatree[5004,720] 1700 includes only BADDRs 1704 with ditto records. Both the current version of the file and the snapshot version of the file are represented by data blocks 100 and 101 on physical storage 1706.

Because the entire file is being overwritten, there is no disadvantage to transferring the list of block addresses corresponding to the current version of the file to the snapshot version of the file. The current version is completely erased, eliminating any need to keep contiguous blocks in the current version of the file. After the adaptive COW process 1800 executes the PITC, the snapshot metatree[5004,720] 1700 includes BADDRs 1704 with block addresses for data blocks 100 and 101 in physical storage 1706.

FIGS. 20C1, 20C2, and 20C3 illustrate two successive partial overwrites of a 144 kB file. FIG. 20C1 illustrates the snapshot version and the current version of the file prior to the first partial overwrite. Prior to the first partial overwrite, the snapshot version and the current version of the file are identical. None of the data blocks of the file have previously been modified. Thus, the snapshot metatree[5004,720] 1700 has a list of BADDRs 1704 that include ditto records, pointing to the corresponding BADDRs 1704 in the current metatree[5004,−1] 1700. Both the current version and the snapshot version of the file include data blocks 100 to 115, 300 and 301 in physical storage 1706. The first partial overwrite is to data blocks 100 to 115 and 330 (0 to 135 kB).

FIG. 20C2 illustrates the snapshot version and the current version of the file after the first partial overwrite. Because the partial overwrite included a sixteen-block cluster of contiguous address space, the adaptive COW process 1800 used PITC to copy the sixteen-block cluster of contiguous address space to the snapshot version of the file. Thus, the block addresses referencing data blocks 100 to 115 in physical storage 1706 were transferred from the current metatree[5004,−1] 1700 to the snapshot metatree[5004,720] 1700. Because the remaining overwritten block, data block 300 (128 to 135 kB), cannot be transferred using PITC without affecting the contiguity of the remaining two-block cluster of the file, this overwritten block is COWed. In other words, if data block 300 were transferred to the snapshot version of the file, a newly allocated data block for the current version of the file (data block 700) would no longer be contiguous with the remaining data block of the current version of the file (data block 301). Thus, data block 300 is COWed. The block address of BADDR[16] 1704 remains with the current metatree[5004,−1] 1700, a new data block 700 is allocated, and BADDR[16] 1704 of snapshot metatree[5004,720] 1700 is assigned the block address of data block 700, replacing the ditto record. Because the last data block of the file was not modified, the snapshot version and the current version of the file both include data block 301. After the overwrite, the current version of the file includes data blocks 500 to 515, 300, and 301 on storage 1706. After the overwrite, the snapshot version of the file includes data blocks 100 to 115, 700, and 301 on storage 1706.

FIG. 20C3 illustrates an example of a partial overwrite of a portion of a file that has been previously COWed. In the illustrated example, the file system overwrites the last two data blocks, data blocks 300 and 301 (128 to 143 kB), of the 144 kB file previously overwritten, as described above with reference to FIG. 20C2. Although the second overwrite includes contiguous data blocks on storage 1706, the adaptive COW process 1800 does not use PITC because one of the data blocks was previously COWed, during the first overwrite described above with reference to FIG. 20C2. Thus, the previously unmodified data block (136 to 143 kB) is COWed. After the second partial overwrite, the last two data blocks of the current version of the file (data blocks 300 and 301) are still contiguous. A newly allocated block now preserves the overwritten data (previously unmodified in the first overwrite) in the snapshot version of the file. Thus, the current version of the file includes data blocks 500 to 515, 300, and 301, and the snapshot version of the file includes data blocks 100 to 115, 700, and 900.

FIG. 20D illustrates a partial delete of a 264 kB file. Prior to the partial delete, the snapshot version and the current version of the file are identical. Both the snapshot version and the current version of the file include data blocks 100 to 115, 300 to 315, and 500. The data blocks are organized into three clusters, including two sixteen-block clusters of contiguous data blocks and a single data block. Because none of the data blocks have been previously modified, the snapshot metatree[5004,720] 1700 has a list of BADDRs 1704 that include ditto records, pointing to the corresponding BADDRs 1704 in the current metatree[5004,−1] 1700. The partial delete starts with data block 115 (120 to 127 kB), the last data block of the first sixteen-block cluster, and continues to the end of the file, also deleting the second sixteen-block cluster, data blocks 300 to 315 (128 to 255 kB), and the single trailing data block, data block 500 (256 to 263 kB).

The adaptive COW process 1800 uses PITC before deleting both the trailing single data block (data block 500) and the second sixteen-block cluster. The partial delete also includes the deletion of a single block within the first sixteen-block cluster (data block 115). Because this data block corresponds to a cluster that is not entirely deleted, this data block is COWed. Thus, a new data block 700 is allocated and the contents of data block 115 are copied to data block 700 prior to the deletion of data block 115. The snapshot metatree[5004,720] 1700 now includes BADDRs 1704 with block addresses for data blocks 700, 300 to 315, and 500 on physical storage 1706. Thus, the current version of the file includes data blocks 100 to 114, and the snapshot version of the file includes data blocks 100 to 114, 700, 300 to 315, and 500.

In some embodiments, an adaptive COW process may use PITC for the single block within the sixteen-block cluster that was not entirely overwritten. The PITC operation may be faster than the COW, and the contiguity of the remaining fifteen blocks would not be affected. Data block 115, however, would not be available for a subsequent append operation, affecting possibly the contiguity of a future current version of the file. One of skill in the art will appreciate that there are different suitable ways to implement an adaptive COW process.

FIG. 20E-1 and 20E-2 illustrate a partial overwrite of a 272 kB file. Prior to the partial overwrite, the snapshot version and the current version of the file are identical. Both the snapshot version and the current version of the file include data blocks 100 to 115, 300 to 315, 500 and 501. Thus, no data blocks in the current version of the file have been modified previously. Accordingly, snapshot metatree[5004,720] 1700 includes BADDRs 1704 with ditto records pointing to the corresponding BADDRs 1704 in the current metatree[5004,−1] 1700. The partial overwrite is of data blocks 108 to 115, 300 to 315, and 500 (64 to 263 kB).

The file includes data blocks corresponding to three different clusters including two sixteen-block clusters and a two-block cluster. The partial overwrite affects all three clusters. The partial overwrite affects the last eight blocks (64 to 127 kb) of the first sixteen-block cluster (0 to 127 kB). It also overwrites the entire second sixteen-block cluster (128 to 255 kB). Finally, it overwrites the first data block (256 to 263 kB) of the two-block cluster. Because the second sixteen-block cluster is completely overwritten and because no blocks have been previously COWed, the second sixteen-block cluster (blocks 300 to 315) is copied using PITC. Because the entire first sixteen-block cluster (blocks 100 to 115) is not overwritten, the last eight blocks (data blocks 108 to 115) are copied using COW. Similarly, because the entire two-block cluster (data blocks 500 and 501) is also not entirely overwritten, the first overwritten block (data block 500) is also copied using COW. After the partial overwrite, the current version of the file includes data blocks 100 to 115, 900 to 915, 500 and 501, which are all contiguous within their respective sixteen-block maximum clusters. The current version of the file includes data blocks 100 to 107, 700 to 707, 300 to 315, 1100, and 501. The block addresses of data blocks 300 to 315 were transferred from the current metatree[5004,−1] 1700 to the snapshot metatree[5004,720] 1700. The BADDRs 1704 in the current metatree[5004,−1] were assigned the block addresses for the newly allocated data blocks 900 to 915. The BADDRs 1704 in the snapshot metatree[5004,720] 1700 were assigned the block addresses for the newly allocated data blocks 700 to 707 and 1100.

XIV. Snapshot Portals

As described above with reference to FIG. 2B, to access snapshot data, users may navigate, in some embodiments, through a snapshot portal (a snapshot/ directory), a special directory that includes snapshots of directories in the file system. In some embodiments, snapshots of the same directory may be accessed through many multiple portals. Because there are multiple possible paths to the same snapshot directory, the file system tracks how a directory was entered in order to facilitate subsequent ascent to an expected parent directories. In some embodiments, the expected parent directory of a particular directory is the parent directory from which the particular directory was entered. In other words, in some embodiments, the expected path for ascent is the path previous path of descent. It is possible to track a directory entry without duplicating stored data for each possible path and without explicitly recording the path entry point. In one embodiment, a directory identifier (LIN), a snapshot identifier (snapid), and a depth value are tracked to allow entry into a child directory and exit back through the same parent directory. An example file system is discussed to illustrate snapshot portals in more detail.

A. Example Directory

FIG. 21 illustrates the embodiment of a file system hierarchy described above with reference to FIG. 2B. FIG. 21 illustrates only portions of the file system hierarchy illustrated in FIG. 2B—specifically, the portions that are relevant to the directory dir1/ 205 (“/ifs/data/dir1/”). Ellipses in FIG. 21 represent portions of the file system hierarchy illustrated in FIG. 2B that are omitted in FIG. 21.

As illustrated in FIG. 2A, dir1/ 205 is included in two snapshots: snapshot one 221 (also called “SNAP1” or “snap1”) with snapshot ID 497 and snapshot two 222 (also called “SNAP2” or “snap2”) with snapshot ID 498. As described above with reference to FIG. 2B, snapshot data may be accessed by navigating through virtual directories. The top-most virtual directory is the entry point to the snapshot data; it is the “.snapshot directory” and is also referred to below as the “snapshot portal” (or “portal”). There are three snapshot portals through which a user may enter to access the snapshots of directory dir1/ 205. These are: .snapshot/ directory 231 in the dir1/ 205 directory, .snapshot/ directory 244 in the data/ 203 directory, and .snapshot/ directory 263 in the /ifs/ 201 directory. Thus, the three portals correspond to each one of the directories in the path /ifs/data/dir1/. In the illustrated embodiment, there is a portal for each directory in which there is some data for which a snapshot has been requested. It will be appreciated by one skilled in the art that there are other suitable ways to implement snapshot portals, including not maintaining a portal for each directory in which there is some data for which a snapshot has been requested.

The .snapshot/ directories 263, 244, and 231 (the snapshot portals) include subdirectories for the snapshots that have been requested for the data accessible through the portal. For example, the .snapshot/ directory 263 (the portal for the /ifs/ directory 201) includes subdirectories snap1/ 264 and snap2/ 274 (both relevant to dir1/ 205), as well as subdirectory snap3/ 278 (not illustrated here because it is not relevant to dir1/ 205). The .snapshot/ directory 244 (the portal for the data/ directory 203) includes subdirectories snap1/ 282 and snap2/ 286 (both relevant to dir1/ 205), as well as subdirectory snap3/ 290 (not illustrated here because it is not relevant to dir1/ 205). Finally, the snapshot/ directory 231 (the portal for the dir1/ directory 205) includes subdirectories snap1/ 232 and snap2/ 235. It does not include a subdirectory for snapshot three 223 because snapshot three 223 does not include any data within the dir1/ directory 205.

Thus, in the illustrated embodiment, the three portals—through which snapshot data in dir1/ 205 may be accessed—include two snapshot subdirectories (corresponding to the two snapshots relevant to dir1/ 205). Thus, there are a total of six snapshot directories corresponding to dir1/ 205—three directories (corresponding to the three portals) for snapshot one 221 and three directories (corresponding to the three portals) for snapshot two 222. The pathnames of each of these six directories is illustrated in FIG. 23A, described in greater detail below.

Because there are three different directory paths for entering a snapshot of dir1/ 205, there are also three possible exit points for returning from a snapshot of dir1/ 205. For example, if a user desires to exit the snapshot of dir1/ 205 corresponding to snapshot one 221—by, for example, executing a “cd.” in a UNIX shell—the user might expect to return to one of three directories, including: .snapshot/ 231 (“/ifs/data/dir1/.snapshot/”), snap1/ 282 (“/ifs/data/.snapshot/snap1”), or data/ 265 (“/ifs/.snapshot/snap1/data/”). In the embodiments described below, the user exits to the directory from which the user entered. To distinguish between directories that correspond to the same snapshot data, the embodiments described below describe the files in the file system 200 with the following fields: LIN, snapid, and depth.

1. LIN

In some embodiments, the files and directories in file system 200 are assigned a unique identifier, such as, for example, a LIN. Thus, for example, dir1/ 205, the current version of “dir1”, is assigned a LIN of “100”. In some embodiments, the directories corresponding to the snapshot versions of a directory share the same LIN as the current version. Thus, for example, dir1/ 205 (the current version of dir1/ represented by the path “/ifs/data/dir1/”) has the same LIN as snap1/ 232 (the snapshot version for snapshot one 221 of dir1/ represented by the path “/ifs/data/dir1/.snapshot/snap1/”) and snap2/ 235 (the snapshot version for snapshot two 222 of dir1/ represented by the path “/ifs/.snapshot/snap1/data/dir1/”). Furthermore, the snapshot directories that are accessible through portals of other directories also share the same LIN as the current version. Thus, for example, dir1/ 246 (“/ifs/data/.snapshot/snap1/dir1/”), dir1/ 287 (“/ifs/data/.snapshot/snap2/dir1”), dir1/ 266 (“/ifs/.snapshot/snap1/data/dir1/”), and dir1/ 275 (“/ifs/.snapshot/snap2/data/dir1/”) also share the same LIN of “100”. Additionally, the .snapshot directory (portal) of a directory also shares the same LIN. Thus, snapshot/ directory 231 (the portal for dir1/ 205) has a LIN of “100”.

2. Snapid

In the illustrated embodiments, the snapshots are assigned a unique identifier, such as, for example, a snapid. Thus, for example, snapshot one 221 is assigned snapid “497”, and snapshot two 222 is assigned snapid “498”. In some embodiments, snapids may be certain special values that indicate specific types of files. For example, a snapid of “−1” may indicate the current version of a file, or a snapid of “−2” may indicate a snapshot portal. Directories within the same snapshot share the same snapid. Thus, for example, dir1/ 266 (“/ifs/.snapshot/snap1/data/dir1/”), data/ 265 (“/ifs/.snapshot/snap1/data/”), and snap1/ 264 (“/ifs/.snapshot/snap1”) all share the same snapid of “497”, but different LINs. This is also true for the different directories (accessible through different portals) corresponding to the same snapshot directory. Thus, for example, snap1/ 232 (“/ifs/data/dir1/.snapshot/snap1/”), dir1/ 246 (“/ifs/data/.snapshot/snap1/dir1/”), and dir1/ 266 (“/ifs/.snapshot/snap1/data/dir1/”) also share the same snapid of “497”.

3. Depth

In the illustrated embodiments, some directories will share both the same LIN and snapid if they correspond to the same directory and the same snapshot. For example, snap 1/ 232 (“/ifs/data/dir1/.snapshot/snap1/”), dir1/ 246 (“/ifs/data/.snapshot/snap1/dir1/”), and dir1/ 266 (“/ifs/.snapshot/snap1/data/dir1/”) all share the same snapid of “497” and also the same LIN of “100”. Accordingly, these directories are distinguished instead by a depth field. The depth field indicates how far a particular snapshot directory is from its respective snapshot portal. Thus, snap1/ 232 has a depth of “1”, dir1/ 246 has a depth of “2”, and dir1/ 266 has a depth of “3”. In some embodiments, snapshot portals and the current versions of files do not have a depth. For example, snapshot portals and current versions of files may have depths of “0”.

B. Example Processes

There are two ways in which the file system hierarchy is typically traversed. First, a request may descend the file system hierarchy, such as for example to access a subdirectory of the relevant directory (the directory from which the request is descending). Second, a request may ascend the file system hierarchy, such as for example to access the parent directory of the relevant directory (the directory from which the request is ascending). It is noted that a request may access a file system hierarchy using an absolute address, which explicitly designates the directory being accessed.

The following provides one embodiment of a process, used by the systems and methods described herein, to descend the file system hierarchy using the identifier of the relevant directory. The file system determines the identifier of the requested child using the identifier of the relevant directory and the name of the requested child. One embodiment of this process is described in greater detail below with reference to FIGS. 22A and 22B. The following also provides one embodiment of a process, used by the systems and methods described herein, to ascend the file system hierarchy using the identifier of the relevant directory. The file system determines the identifier of the parent, from which the user entered into the relevant directory, using the identifier of the relevant directory. One embodiment of this process is described immediately below with reference to FIGS. 22C and 22D.

With reference to the below, it is helpful to consider an example of a change to the current version of the file system hierarchy after a snapshot has been taken. For example, if dir1/ 205 (LIN of “100”) were moved from /ifs/data/ to /ifs/ after the creation of snapshot one 221, then the LIN of the parent of (hypothetical) current node /ifs/dir1/ would be “2”, indicating /ifs/ 201. This information is relevant to ascending/descending the current portions of the file system hierarchy. For the snapshot data (/ifs/.snapshot/snap1/data/dir1/, /ifs/data/.snapshot/snap1/dir1/, and /ifs/data/dir1/.snapshot/snap1), however, the relevant information for ascending/descending is the LIN of the parent of dir1/ 205 at the time of the snapshot. At the time of the snapshot, data/ 203 was the parent of dir1/ 205, so the LIN of “4” is the relevant information for the snapshot versions of dir1/ 205 because that is the LIN of the parent of dir1/ 205 at the time the snapshot was taken.

1. Descending the Hierarchy

FIGS. 22A and 22B illustrate flowcharts of one embodiment of determining the designated child directory of a relevant directory by returning the identifier of the requested child using the identifier of the relevant directory. In some embodiments, the instructions of FIGS. 22A and 22B are stored in a module—such as, for example, a navigation module or the snapshot module 113—and run by a return child process 2200 of a computing system. With reference to FIG. 22A, the return child process 2200 receives, in state 2202, the LIN, snapid, and depth of the relevant directory, as well as the name of a child in the relevant directory. In state 2204, the return child process 2204 returns the LIN, snapid, and depth of the requested child of the relevant directory.

FIG. 22B illustrates in greater detail state 2204, described above with reference to FIG. 22A. As described above, an identifier of a file or directory in a file system hierarchy may include the combination of LIN, snapid, depth values. Using the identifier (LIN, snapid, and depth) of the relevant directory, as well as the name of the requested child, the return child process 2200 determines the identifier (LIN, snapid, and depth) of the requested child. Unless specifically modified, the LIN, snapid, and depth values (of the requested child) returned by the return child process 2200 are the values received by the return child process 2200 for the relevant directory. In other words, the LIN, snapid, and/or depth of the requested child are the same as those of the relevant directory unless specifically modified by the return child process 2200.

In state 2206, the return child process 2200 determines whether the snapid of the relevant directory is a special number indicating that the relevant directory is the current version of the directory. For example, a special number of “−1” may indicate, in some embodiments, the current version of the directory. If the snapid indicates that the relevant directory is the current version of the directory, then the return child process determines, in state 2208, whether the requested name of the child is “.snapshot”. If the requested name is “.snapshot,” then the requested child is the snapshot portal of the relevant directory. In other words, the request is a request to enter snapshot data in the file system hierarchy. The return child process 2200 then proceeds, in state 2210, to change the snapid to “−2,” indicating that the requested child directory is the snapshot/ or portal directory. The LIN and the depth of a portal are the same as its parent, so the LIN and the depth remain unchanged. The return child process 2200 then proceeds to state 2224, returning the unchanged LIN, the changed snapid, and the unchanged depth. If the requested name is not “.snapshot,” then the requested child is not a portal, but rather a child of a directory that is not a snapshot directory. Thus, the return child process 2200 proceeds, in state 2212, to change the LIN to be the LIN of the requested child, and leaves the snapid and the depth unchanged. To determine the LIN of the requested child, the return child process 2200 may call a process (not illustrated) that uses, for example, the LIN of the relevant directory, the unchanged snapid (indicating that the relevant directory is a current version of a directory), and the requested child name. The return child process 2200 then proceeds to state 2224 and returns the changed LIN, the unchanged snapid, and the unchanged depth.

If the snapid is not a special number indicating the current version of the file, then the return child process 2200 determines, in state 2214, whether the snapid is a special number indicating a portal. For example, the value of “−2” may indicate a portal. If the snapid is a special number indicating a portal, then the return child process 2200 proceeds, in state 2216, to change the snapid to the snapid of the snapshot version corresponding to the requested child. In other words, if the relevant directory is the portal of a snapshot, then the requested child will be the name of one of the snapshot versions. For example, with reference to FIG. 21, if the relevant directory is .snapshot/ 263 (“ifs/.snapshot/”), then a request descending from .snapshot/ 263 may request the snapshot directory corresponding to snapshot one 221 (snap1/ 264) with snapid “497”, snapshot two 222 (snap2/ 274) with snapid “498”, or (illustrated in FIG. 2B-2) snapshot three 223 (snap3/ 278) with snapid “720”. Thus, if a user requests “snap1/”, the return snapid would be assigned the value “497”. Then, the return child process 2200 changes, in state 2218, the depth to a value indicating that the requested child is a child of a portal (or, in other words, is one generation removed from a portal). In some embodiments, the depth of a child of a portal is “1”. The LIN remains unchanged because the LIN of a child of a portal is the same as the LIN of the portal. The return child process 2200 then returns, in state 2224, the unchanged LIN, the changed snapid, and the changed depth.

If the snapid is not a special number indicating a portal (or the current version of the file, as determined in state 2206), then the snapid indicates a particular snapshot version, and the relevant directory is one of the directories corresponding to that particular snapshot version. In other words, the relevant directory is a descendent of a portal. In some embodiments, the descendents of a portal—the snapshot directories—have unique LINs, as they correspond to unique files (the current versions) in the file system 200. Thus, in state 2220, the return child process 2200 changes the LIN to be the LIN of the requested child of the current version of the relevant directory (a snapshot version) at the time the snapshot was taken. The return child process 2200 looks for the LIN of the requested child of the current version at the time the snapshot was taken because the children of the current version may have changed since the snapshot was taken. To determine the LIN of this requested child, the return child process 2200 may call a process (not illustrated) that uses, for example, the LIN and snapid of the relevant directory and the requested child name. In state 2222, the return child process 2200 increments the depth by a value of one, as the child is one level more away from the portal. The depth distinguishes different instances of the snapshot directory in the file system hierarchy. The descendents of a portal share the same snapid, so the snapid remains unchanged. The return child process 2200 then returns, in state 2224, the changed LIN, the unchanged snapid, and the changed depth.

2. Ascending The Hierarchy

FIGS. 22C and 22D illustrate flowcharts of one embodiment of determining the relevant directory's parent directory by returning the identifier of the parent directory (through which the relevant directory was entered) using the identifier of the relevant directory. In some embodiments, the instructions of FIGS. 22C and 22D are stored in a module—such as, for example, a navigation module or the snapshot module 113—and run by a return parent process 2250 of a computing system. In state 2252, return parent process 2250 receives an identifier (for example, LIN, snapid and depth) of the relevant directory. In state 2254, the return parent process 2250 returns the identifier of the parent directory of the relevant directory from which the user originally entered the relevant directory.

FIG. 22D illustrates in greater detail state 2254 described above with reference to FIG. 22C. As described above, an identifier of a file or directory in a file system hierarchy may include the combination of LIN, snapid, depth values. Using the identifier (LIN, snapid, and depth) of the relevant directory, the return parent process 2250 determines the identifier (LIN, snapid, and depth) of the parent directory from which the relevant directory was entered. Unless specifically modified, the LIN, snapid, and depth values (of the requested child) returned by the return parent process 2250 are the values received by the return parent process 2200 for the relevant directory. In other words, the LIN, snapid, and/or depth of the parent are the same as those of the relevant directory unless specifically modified by the return parent process 2250.

In state 2256, the return parent process 2250 determines whether the snapid of the relevant directory is a special number indicating the relevant directory is the current version of the directory and not a snapshot version. For example, in some embodiments a value “−1” may indicate the current version of a directory and not a snapshot version. If the snapid of the relevant directory indicates the current version of the directory and not a snapshot version, then the identifier of the parent is the same as the relevant directory, except for the LIN. This is the case because the parent directory of a current version is also a current version (of the parent directory), so the snapid of the parent will also be, for example, “−1” and the depth of the parent will also remain, for example, “0”. Thus, the return parent process 2250 proceeds, in state 2258, to change the LIN to be the LIN of the parent directory, and the snapid and the depth remain unchanged. To determine the LIN of the parent, the return parent process 2250 may call a process (not illustrated) that uses, for example, the LIN of the relevant directory and the unchanged snapid (indicating that the relevant directory is a current version of a directory). Then, in state 2270, the return parent process 2250 returns the changed LIN, the unchanged snapid, and the unchanged depth.

If the snapid of the relevant directory does not indicate that it is the current version of the file, then the relevant directory must be either a snapshot portal (a .snapshot/ directory) or a snapshot directory. In state 2260, the return parent process 2250 determines whether the snapid is a special number indicating that the relevant directory is a portal. For example, in some embodiments, a value of “−2” may indicate that the relevant directory is a portal. If the relevant directory is a portal, then the parent directory is the current version of the parent directory. Thus, the return parent process 2250 proceeds, in state 2262, to change the snapid to the special number indicating the current version of the directory, for example “−1”. The LIN remains unchanged, as the portal has the same LIN as the current version of the portal's parent directory. Similarly, the depth remains unchanged, as the portal and the current version of a directory both have a depth of, for example, “0”. Then, in state 2270, the return parent process 2250 returns the unchanged LIN, the changed snapid, and the unchanged depth.

If the relevant directory is not a portal (and also not the current version of the directory, as already determined in state 2256), then it is a snapshot directory or, in other words, a descendent of the portal. In some embodiments, the descendents of a portal have a depth that is equal to the number of generations of separation between the descendent and the portal. The parent of a portal descendent is one generation closer to the portal. Thus, the return parent process 2250 proceeds, in state 2264, to decrement the depth by, for example, one. Then, the return parent process 2250 determines, in state 2266, whether the depth indicates that the relevant directory would return to a portal. In other words, the return parent process 2250 determines whether the relevant directory is a child directory of a portal directory. In some embodiments, the value “0” after the decrement may indicate that the parent directory is a snapshot portal. If the relevant directory is a child directory of a portal, then its depth, in some embodiments, would be “1”, indicating that it is one generation away from the portal. After decrementing the depth, in state 2264, the depth value would be “0”. If the decremented depth value indicates that the relevant directory is returning to a portal (in other words, that the relevant directory is a child of a portal), then the return parent process 2250 proceeds, in state 2268, to change the return snapid to be the special number indicating a snapshot portal, for example “−2”. The LIN remains unchanged because the LIN of a child of a portal corresponds to the LIN of the parent directory of the portal—in other words, the current version of the directory in which the portal is found. The return parent process 2250 then proceeds, in state 2270, to return the unchanged LIN, the changed snapid, and the changed depth.

If the depth does not indicate that the parent directory is a portal, then the relevant directory is a descendent of a child of a portal, and the parent of the relevant directory is a descendent, including possibly a child, of a portal—in other words, a snapshot directory. In some embodiments, the descendents of a portal (the snapshot directories) have unique LINs, as they correspond to unique files (the current versions) in the file system 200. Thus, the return parent process 2250, then, changes, in state 2267, the LIN to be the LIN of the parent of the current version of the relevant directory (a snapshot version) at the time the snapshot was taken. The return process 2250 looks for the LIN of the parent of the current version at the time the snapshot was taken because the parent of the current version may have changed since the snapshot. To determine the LIN of this parent, the return parent process 2250 may call a process (not illustrated) that uses, for example, the LIN and snapid of the relevant directory. In the illustrated embodiment, the descendents of a child of a portal have unique LINs, as they provide access to a snapshot of a unique file in the file system 200. The LINs of the descendents of a child of a portal are also different than the LIN of the child. However, the descendents of a child of a portal and the child of a portal share the same snapid, so the snapid remains unchanged. The return parent process 2250 then proceeds, in state 2270, to return the changed LIN, the unchanged snapid, and the changed depth.

C. Example Directories

FIG. 23A illustrates the identifiers for the six snapshot directories corresponding to directory dir1/ 205. These snapshot directories have different identifiers, which uniquely identify their respective position in the file system hierarchy. Because each of these snapshot directories is a snapshot of dir1/ 205, the identifiers of the six snapshot directories have the same LIN of “100”, which is the LIN corresponding to directory dir1/ 205. Three of the snapshot directories correspond to snapshot one 221 and, therefore, their identifiers have a snapid of “497”. The other three directories correspond to snapshot two 222 and, therefore, have a snapid of “498”. As described above, with reference to FIG. 21A, there are three different snapshot directories, per snapshot, corresponding to dir1/ 205. Thus, with respect to snapshot one 221, the following three snapshot directories correspond to the same snapshot data of the same directory (dir1/ 205): snap1/ 232 (“/ifs/data/dir1/.snapshot/snap1/”), dir1/ 246 (“/ifs/data/.snapshot/snap1/dir1/”), and dir1/ 266 (“/ifs/.snapshot/snap1/data/dir1/”). In order to distinguish these three snapshot directories, which are descendents of different portals, a depth field is kept. A depth of “1” indicates that a snapshot directory (a descendent of a particular portal) is one generation from its portal. With respect to snapshot one 221, the only snapshot directory corresponding to dir1/ 205 that is one generation from the portal is snap1/ 232 (“/ifs/data/dir1/.snapshot/snap1/”). A depth of “2” indicates that a snapshot directory is two generations from its portal. With respect to snapshot one 221, the only subdirectory corresponding to dir1/ 205 that is two generations from the portal is dir1/ 246 (“/ifs/data/.snapshot/snap1/dir1/”). A depth of “3” indicates that a snapshot directory is three generations from its portal. With respect to snapshot one 221, the only subdirectory corresponding to dir1/ 205 that is three generations from the portal is dir1/ 266 (“/ifs/.snapshot/snap1/data/dir1/”).

FIGS. 23B, 23C, and 23D illustrate examples of descending and ascending the file system hierarchy of FIG. 21 using an identifier including a LIN, snapid, and depth. Although the examples described below are with reference to snapshot directories in snapshot one 221, the same examples would operate similarly for snapshot directories in snapshot two 222.

FIG. 23B illustrates examples of descending from /ifs/ 201 to snap1/ 232, and then ascending back through the same path. The directory /ifs/ 201 is identified by a LIN of “2”, a snapid of “−1” (the current version of its file), and a depth of“0” (current versions of files have no depth). From state 2300 to state 2302, the user requests to navigate from /ifs/ 201 to data/ 203. Because the relevant directory (/ifs/ 201) is the current version of its file and because the requested child (data/ 203) is not a portal, the return child process 2250 returns an identifier with a LIN of “4” (the LIN of the requested child), a snapid of “−1” (the requested child is the current version of its file), and a depth of “0” (current versions of files have no depth). From state 2302 to 2304, the user requests to navigate from data/ 203 to dir1/ 205. Because the relevant directory (data/ 203) is the current version of its file and because the requested child (dir1/ 205) is not a portal, the return child process 2250 returns an identifier with a LIN of “100” (the LIN of the requested child), a snapid of “−1” (the requested child is the current version of its file), and a depth of “0” (current versions of files have no depth). From state 2304 to state 2306, the user requests to navigate from dir1/ 205 to .snapshot/ 231, the portal of dir1/ 205. Because the relevant directory (dir1/ 205) is the current version of its file and because the requested child (.snapshot/ 231) is a portal, the return child process 2250 returns the same LIN and depth of the relevant directory, but the snapid returned is “−2” (the requested child is a portal). From state 2306 to state 2308, the user requests to navigate from .snapshot/ 231 to the snapshot directory snap1/ 232. Because the relevant directory (.snapshot/ 231) is a portal, the return child process 2250 returns a LIN of “100” (a child of a portal has the same LIN as the portal), a snapid of “497” (the snapshot version which the user desires to enter), and a depth of “1” (the requested child is one generation from the portal).

From state 2308 to state 2310, the user requests to navigate from snap1/ 232 back to .snapshot/ 231. Logically, there are, at least, three different directories to which the file system might return, including .snapshot/ 231 (“/ifs/data/dir1/.snapshot/snap1/”), snap1/ 282 (“/ifs/data/.snapshot/snap1/”), and data/ 265 (“/ifs/.snapshot/snap1/data/”). In the illustrated embodiments, the file system returns the user to the parent directory from which the user entered. Return parent process 2200 implements this design decision. Accordingly, because the relevant directory (snap1/ 232) is a child of a portal, the return parent process 2200 returns a LIN of “100” (a portal has the same LIN as its children), a snapid of “−2” (the parent is a portal), and a depth of “0” (portals do not have depth). From state 2310 to state 2312 the user requests to exit the portal by navigating from .snapshot/ 231 to dir1/ 205, which is the current version of its file. Because the relevant directory (.snapshot/ 231) is a portal, the return parent process 2200 returns a LIN of “100” (a portal's parent, the current version of its file, has the same LIN as the portal), a snapid of “−1” (the parent of a portal is the current version of its file), and a depth of “0” (current versions have no depth). From state 2312 to 2314 the user requests to navigate from dir1/ 205 to data/ 203. Because the relevant directory (dir1/ 205) is a current version of its file, the return parent process 2200 returns a LIN of “4” (the LIN of the parent of the relevant directory), a snapid of “−1” (the parent of a current version is also a current version), and a depth of “0” (current versions have no depth). From state 2314 to 2316, the user requests to navigate from data/ 203 back to /ifs/ 201. Because the relevant directory (data/ 203) is the current version of its file, the return parent process 2200 returns a LIN of “2” (the LIN of the parent of the relevant directory), a snapid of “−1” (a parent of a current version is also a current version), and a depth of “0” (current versions have no depth).

FIG. 23C illustrates examples of descending from /ifs/ 201 to dir1/ 246, and then ascending back through the same path. From state 2320 to state 2322, the user requests to navigate from /ifs/ 201 to data/ 203. Because the relevant directory (/ifs/ 201) is the current version of its file and because the requested child (data/ 203) is not a portal, the return child process 2250 returns an identifier with a LIN of “4” (the LIN of the requested child), a snapid of “−1” (the requested child is the current version of its file), and a depth of “0” (current versions of files have no depth). From state 2322 to 2324, the user requests to navigate from data/ 203 to .snapshot/ 244. Because the relevant directory (data/ 203) is the current version of its file and because the requested child (.snapshot/ 244) is a portal, the return child process 2250 returns the same LIN and depth of the relevant directory, but the snapid returned is “−2” (the requested child is a portal). From state 2324 to state 2326, the user requests to navigate from .snapshot/ 244 to the snapshot directory snap1/ 282. Because the relevant directory (.snapshot/ 244) is a portal, the return child process 2250 returns a LIN of “4” (a child of a portal has the same LIN as the portal), a snapid of “497” (the snapshot version which the user desires to enter), and a depth of “1” (the requested child is one generation from the portal). From state 2326 to state 2328, the user requests to navigate from snap1/ 282 to dir1/ 246. Because the relevant directory (snap1/ 282) is a snapshot directory, the return child process 2250 returns a LIN of “100” (the LIN of the requested child), snapid of “497” (a child of snapshot directory has the same snapid), and a depth of “2” (the requested child is two generations from the portal).

From state 2328 to state 2330, the user requests to navigate from dir1/ 246 back to snap1/ 282. Because the relevant directory (dir1/ 246) is a snapshot directory and because its parent (snap1/ 282) is not a portal, the return parent process 2200 returns a LIN of “4” (the LIN of the parent), a snapid of “497” (a parent of a snapshot directory has the same snapid), and a depth of “1” (the parent is one generation from the portal). From state 2330 to 2332, the user requests to navigate from snap1/ 282 back to .snapshot/ 244. Because the relevant directory (snap1/ 282) is a child of a portal, the return parent process 2200 returns a LIN of “4” (a portal has the same LIN as its children), a snapid of “−2” (the parent is a portal), and a depth of “0” (portals do not have depth). From state 2332 to state 2334, the user requests to exit the portal by navigating from snapshot/ 244 to data/ 203, which is the current version of its file. Because the relevant directory (.snapshot/ 244) is a portal, the return parent process 2200 returns a LIN of “4” (a portal's parent, the current version of its file, has the same LIN as the portal), a snapid of “−1” (the parent of a portal is the current version of its file), and a depth of “0” (current versions have no depth). From state 2334 to 2336, the user requests to navigate from data/ 203 back to /ifs/ 201. Because the relevant directory (data/ 203) is the current version of its file, the return parent process 2200 returns a LIN of “2” (the LIN of the parent of the relevant directory), a snapid of “−1” (a parent of a current version is also a current version), and a depth of “0” (current versions have no depth).

FIG. 23D illustrates examples of descending from /ifs/ 201 to dir1/ 266, and then ascending back through the same path. From state 2340 to state 2342, the user requests to navigate from /ifs/ 201 to .snapshot/ 263. Because the relevant directory (/ifs/ 201) is the current version of its file and because the requested child (.snapshot/ 244) is a portal, the return child process 2250 returns the same LIN and depth of the relevant directory, but the snapid returned is “−2” (the requested child is a portal). From state 2342 to state 2344, the user requests to navigate from .snapshot/ 263 to the snapshot directory snap1/ 264. Because the relevant directory (.snapshot/ 263) is a portal, the return child process 2250 returns a LIN of “2” (a child of a portal has the same LIN as the portal), a snapid of “497” (the snapshot version which the user desires to enter), and a depth of “1” (the requested child is one generation from the portal). From state 2344 to state 2346, the user requests to navigate from snap1/ 264 to data/ 265. Because the relevant directory (snap1/ 264) is a snapshot directory, the return child process 2250 returns a LIN of “4” (the LIN of the requested child), snapid of “497” (a child of snapshot directory has the same snapid), and a depth of “2” (the requested child is two generations from the portal). From state 2346 to 2348, the user requests to navigate from data/ 265 to dir1/ 266. Because the relevant directory (data/ 265) is a snapshot directory, the return child process 2250 returns a LIN of “100” (the LIN of the requested child), snapid of “497” (a child of a snapshot directory has the same snapid), and a depth of “3” (the requested child is three generations from the portal).

From state 2348 to state 2350, the user requests to navigate from dir1/ 266 to data/ 265. Because the relevant directory (dir1/ 266) is a snapshot directory and because its parent (data/ 265) is not a portal, the return parent process 2200 returns a LIN of “4” (the LIN of the parent), a snapid of “497” (a parent of a snapshot directory has the same snapid), and a depth of “1” (the parent is one generation from the portal). From state 2350 to 2352, the user requests to navigate from data/ 265 back to snap1/ 264. Because the relevant directory (data/ 265) is a snapshot directory and because its parent (snap1/ 264) is not a portal, the return parent process 2200 returns a LIN of “2” (the LIN of the parent), a snapid of “497” (a parent of a snapshot directory has the same snapid), and a depth of “2” (the parent is two generations from the portal). From state 2352 to 2354, the user requests to navigate from snap1/ 264 back to .snapshot/ 263. Because the relevant directory (snap1/ 264) is a child of a portal, the return parent process 2200 returns a LIN of “2” (a portal has the same LIN as its children), a snapid of “−2” (the parent is a portal), and a depth of “0” (portals do not have depth). From state 2354 to state 2356, the user requests to exit the portal by navigating from .snapshot/ 263 to /ifs/ 201, which is the current version of its file. Because the relevant directory (.snapshot/ 263) is a portal, the return parent process 2200 returns a LIN of “2” (a portal's parent, the current version of its file, has the same LIN as the portal), a snapid of “−1” (the parent of a portal is the current version of its file), and a depth of “0” (current versions have no depth).

XV. Other Embodiments

While certain embodiments of the invention have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the present invention.

By way of example, the following alternatives are also contemplated. Although the data structures described herein have been directed to a distributed system, some embodiments of the invention may be used in a single file system. Additionally or alternatively, it will be recognized by one with ordinary skill in the art that the depicted embodiments may be modified to accommodate file structures under the logical model, physical model, hybrid model and/or log-based model. Further, in addition to adding the snapshot ID to the root of the snapshot upon snapshot creation, the snapshot ID may be added to some or all of the files and directories governed by the snapshot. Additionally, it is recognized that the root of a snapshot can be a single file or directory or more than one file or directory. Embodiments of a systems and methods for performing a reverse lookup are disclosed in U.S. patent application Ser. No. 11/507,075, titled “SYSTEMS AND METHODS OF REVERSE LOOKUP,” filed on Aug. 18, 2006, and is hereby incorporated by reference in its entirety.

The above-mentioned alternatives are examples of other embodiments, and they do not limit limit the scope of the invention. It is recognized that a variety of data structures with various fields and data sets may be used. In addition, other embodiments of the flow charts may be used. 

1. A method of ascending a file system capable of distinguishing, based on relative depth, between multiple unique paths to the same directory, the method comprising: receiving a request to ascend from a child directory to an expected parent directory, the expected parent directory being one of multiple possible parent directories; determining the expected parent directory by evaluating, in part, a relative depth value of the child directory; and ascending to the expected parent directory.
 2. The method of claim 1, wherein the ascending to the expected parent directory is part of ascending the file system through a path that was taken when descending the file system.
 3. The method of claim 1, wherein the file system is a distributed file system.
 4. The method of claim 2, wherein the file system is a distributed file system.
 5. The method of claim 1, wherein the file system is a multiple-version file system comprising current versions of data, snapshot versions of data, and portals to snapshots of data.
 6. The method of claim 2, wherein the file system is a multiple-version File system comprising current versions of data, snapshot versions of data, and portals to snapshots of data.
 7. The method of claim 5, wherein the snapshot versions of data are per-directory snapshots.
 8. The method of claim 5, wherein the child directory is a snapshot version of data.
 9. The method of claim 8, further comprising calculating the relative depth when descending into the child directory.
 10. The method of claim 5, wherein the expected parent directory comprises one of the following: a snapshot version of data, a portal to snapshot data, and a current version of data.
 11. The method of claim 5, wherein the determining further comprises determining whether the child directory is one of the following: a current version of data, a portal to snapshot data, and a snapshot version of data.
 12. The method of claim 5, wherein the relative depth is relative to one of the following: a snapshot version of data, a portal to snapshot data, and a current version of data.
 13. A system capable of ascending a file system by distinguishing, based on relative depth, between multiple unique paths to the same directory, the system comprising: a processor; a memory system coupled to the processor, the memory system storing a file system; and a navigation module comprising instructions executable by the processor to operate on the file system, the instructions comprising: receiving a request to ascend from a child directory to an expected parent directory, the expected parent directory being one of multiple possible parent directories; determining the expected parent directory by evaluating, in part, a relative depth value of the child directory; and ascending to the expected parent directory.
 14. The system of claim 13, wherein the ascending to the expected parent directory is part of ascending the file system through a path that was taken when descending the file system.
 15. The system of claim 13, wherein the file system is a distributed file system.
 16. The system of claim 14, wherein the file system is a distributed file system.
 17. The system of claim 13, wherein the file system is a multiple-version file system comprising current versions of data, snapshot versions of data, and portals to snapshots of data.
 18. The system of claim 14, wherein the file system is a multiple-version file system comprising current versions of data, snapshot versions of data, and portals to snapshots of data.
 19. The system of claim 17, wherein the snapshot versions of data are per-directory snapshots.
 20. The system of claim 17, wherein the child directory is a snapshot version of data.
 21. The system of claim 20, wherein the instructions further comprise calculating the relative depth when descending into the child directory.
 22. The system of claim 17, wherein the expected parent directory comprises one of the following: a snapshot version of data, a portal to snapshot data, and a current version of data.
 23. The system of claim 17, wherein the determining further comprises determining whether the child directory is one of the following: a current version of data, a portal to snapshot data, and a snapshot version of data.
 24. The system of claim 17, wherein the relative depth is relative to one of the following: a snapshot version of data, a portal to snapshot data, and a current version of data. 